From charon-fan-agent-playbook
Generates Git commit messages following Conventional Commits spec with types like feat/fix/refactor, scopes, subject/body/footer guidelines, and issue references. Activates on commit requests or git mentions.
npx claudepluginhub zhaono1/agent-playbookThis skill is limited to using the following tools:
A skill for creating properly formatted Git commit messages following the [Conventional Commits](https://www.conventionalcommits.org/) specification.
Generates conventional commit messages from git diffs by analyzing changes for type, scope, and subject. Validates messages against spec and executes git commits after confirmation.
Guides Git commit messages to follow Conventional Commits v1.0.0 spec, covering types (feat, fix, refactor, etc.), scopes, structure, body, footers, and examples. Use for code commits and PR reviews.
Formats Git commit messages according to Conventional Commits spec with types like feat/fix, scopes, bodies, and breaking changes. Enables automated changelogs and semantic versioning. Activates on commit writing or git mentions.
Share bugs, ideas, or general feedback.
A skill for creating properly formatted Git commit messages following the Conventional Commits specification.
This skill activates when you:
<type>(<scope>): <subject>
<body>
<footer>
| Type | Description |
|---|---|
feat | A new feature |
fix | A bug fix |
docs | Documentation only changes |
style | Changes that do not affect the meaning of the code (formatting, etc.) |
refactor | A code change that neither fixes a bug nor adds a feature |
perf | A code change that improves performance |
test | Adding missing tests or correcting existing tests |
chore | Changes to the build process or auxiliary tools |
ci | Changes to CI configuration files and scripts |
build | Changes that affect the build system or external dependencies |
The scope should indicate the area of the codebase affected:
components, hooks, store, styles, utilsapi, models, services, database, authci, deploy, dockerCloses #123, Fixes #456, Refs #789Closes #123, #456, #789BREAKING CHANGE: followed by descriptionfeat(auth): add OAuth2 login support
Implement OAuth2 authentication flow to allow users to log in
with their Google or GitHub accounts.
This change adds:
- New OAuth2 middleware for handling callbacks
- Updated login UI with social login buttons
- User profile synchronization
Closes #123
fix(api): resolve race condition in user creation
The concurrent user creation requests could result in duplicate
email entries. Added unique constraint and proper error handling.
Fixes #456
refactor(user): simplify profile update logic
Extracted common validation logic into a reusable function
to reduce code duplication across profile update endpoints.
docs: update API documentation with new endpoints
Added documentation for the v2 user management endpoints
including request/response examples and error codes.
updated stuff # Too vague, no type/scope
fixed bug # No context about which bug
feat: added feature # Redundant ("feat" means new feature)
Feat(User): Add Login # Incorrect capitalization
feat: A really really really long subject line that exceeds the recommended limit # Too long
When introducing breaking changes, add BREAKING CHANGE: to the footer:
feat(api): migrate to REST v2
The API endpoints have been restructured for better consistency.
Old endpoints are deprecated and will be removed in v3.0.
BREAKING CHANGE: `/api/v1/users` is now `/api/v2/users`.
All consumers must update their integration by 2025-03-01.
When writing a commit message:
git diff to understand what changedUse the validation script to check commit message format:
python scripts/validate_commit.py "your commit message"
references/conventional-commits.md for full specificationreferences/examples.md for more examplesreferences/scopes.md for recommended scope naming