git-commits
Create well-structured git commits. ALWAYS use this skill when committing - even for simple single-file commits. Triggers: "commit", "stage", "add and commit", or after completing any code changes.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: git-commits description: Create well-structured git commits. ALWAYS use this skill when committing - even for simple single-file commits. Triggers: "commit", "stage", "add and commit", or after completing any code changes.
Git Commits
Always invoke this skill for every commit. This ensures consistent, well-structured commits.
Workflow
- Run
git statusandgit diffto see changes - Run
git log --oneline -5to see recent commit style - Determine if changes should be one or multiple commits
- Stage and commit with clear message
When to Split vs Combine
Separate commits:
- CSS vs PHP logic
- Different features (even in same file)
- Refactoring vs new functionality
- Multiple bug fixes (one per fix)
Single commit:
- Related changes for one feature
- A handler + its CSS
- Tests for the feature being added
Commit Message Format
<summary line - what and why, not how>
<optional body with more context>
Examples
Input: Single file change to update details
- $title = __( 'Old title', 'simple-history' );
+ $title = __( 'New title', 'simple-history' );
Output:
Update 5.22.0 update details title
Input: Multiple related changes across files
# file1.php
+ public function new_feature() { ... }
# file2.php
+ add_filter( 'hook', [ $this, 'new_feature' ] );
Output:
Add new feature for X
Register hook and implement handler.
Multiple Repositories
When changes span core + premium:
- Commit core first, then premium
- Use related commit messages
More by bonny
View allRun SQL queries against the WordPress development database. Use when querying database tables, inspecting Simple History events, checking WordPress data, debugging database issues, or when the user says "run query" or "check database".
Provides WordPress coding standards, PHP/CSS/JS style guide, code linting and static analysis (phpcs, phpstan, rector, phpcbf). Use before writing or editing PHP, CSS, or JavaScript code, when fixing lint errors, running code quality tools, or reviewing code style compliance.
Ensures WordPress.org compliance for freemium plugins (free vs premium features, license keys, trial limits, upselling). Prevents trialware violations. Use when adding premium features, implementing upsells, checking license keys, creating teasers, reviewing code before WordPress.org submission, or when the user mentions "premium", "upsell", or "freemium".
Add an entry to the changelog in readme.txt following the project's changelog format. Use when updating readme.txt, adding to Unreleased section, documenting changes for a release, or when the user says "add changelog" or "update changelog".