Loading...
Loading...
Found 38 Skills
Use when writing git commit messages for non-trivial changes — captures decision context (constraints, rejected alternatives, confidence, directives) as structured git trailers so future agents and developers can query project knowledge via git log --trailer=
Generate git commit messages and help with git workflows
Commit Message Specification. Generate commit messages compliant with Conventional Commits based on staged changes, support Chinese descriptions, and automatically handle types, scopes, and breaking changes. Use to write standardized commit messages from staged git changes.
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
Generate appropriate commit messages based on Git diffs
Generates conventional commit messages by analyzing git diffs and changes. Use when writing commit messages, following commit conventions, or documenting changes.
Create standardized git commit messages. Prioritize following the project's existing commit conventions, and support the Conventional Commits format. Usage scenarios: Users request to create commits or write commit messages
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
Generate well-formatted git commit messages following conventional commit standards
This skill MUST be loaded on every git commit without exception. It should also be used when the user asks to "write a conventional commit", "format a commit message", "follow conventional commits spec", "create a semantic commit", "make a commit", "commit changes", or "git commit". Every commit message produced in this project MUST conform to this specification.
Write git commit messages in Angelo Laus's Conventional Commits style (type(scope): lowercase imperative subject, plus a terse "- add/replace/cover" bullet body). Use whenever the user asks for a commit message, shows a diff or staged changes, or says "commit this". Output the message only. Never run git commit.
Standards and quality gates for code comments, JSDoc/docstrings, technical documentation, and git commit messages. Use to evaluate or write high-signal, concise documentation and eliminate AI comment fluff, over-explanation, ghost commentary, commit message storytelling, and stylistic tells.