Write conventional git commit messages with type, scope, and subject.
npx skills add https://github.com/amanpal3/SKILLs --skill commit-amanpal3
Please help me install this Agent Skill. Skill: commit Source: https://github.com/amanpal3/SKILLs/tree/main/.agent/plugins/ralph/skills/commit Command: npx skills add https://github.com/amanpal3/SKILLs --skill commit-amanpal3
type(scope): subject format with enforced rules for types (feat, fix, refactor, security, etc.), kebab-case scopes, and 50-character imperative subjects. - Structured Bodies and Trailers: Supports multi-line bodies explaining HOW and WHY, plus git trailers like Fixes #N, BREAKING CHANGE:, and Co-authored-by for issue linking and semantic-release triggers. - PR and Merge Commit Support: Provides extended formats for pull request descriptions and merge commits with task breakdowns, requirement references, and test coverage summaries. - Use Case: After staging security fixes, ask the agent to commit them and receive a message like fix(auth): use hmac.compare_digest for secure comparison with a body referencing the addressed requirement. ## Quick Start Stage my changes and create a conventional commit message for the authentication fix I just made.High-intent search queries and answers about installing and using this skill.
Use the format `type(scope): subject`, such as `feat(auth): add login endpoint`. Pick a type like feat, fix, or refactor, add a kebab-case scope in parentheses, and write a present-tense imperative subject under 50 characters with no trailing period.
Common types include feat for new features, fix for bug fixes, refactor for code restructuring, perf for performance, test for tests, docs for documentation, ci for pipeline changes, chore for maintenance, style for formatting, and security for vulnerability fixes.
Add an exclamation mark after the scope, like `feat(api)!: change response format`, or include a `BREAKING CHANGE:` footer in the commit body describing the incompatibility. This triggers a major version bump in semantic-release tooling.
Yes, add trailers like `Fixes #123` or `Closes #123` at the end of the commit body after a blank line. GitHub automatically closes the referenced issue when the commit merges into the default branch.
Never commit secrets such as `.env` files or `credentials.json`, dependency folders like `node_modules/` or `.venv/`, or large binary files without explicit approval. Review staged changes with `git diff --staged` before committing.
tldrawCreates a conventional git commit for staged and unstaged working tree changes.
posit-devCreates a GitHub pull request for the current session's changes via the GitHub MCP server.
saleorAutomate pre-commit quality checks with lint fixes, TypeScript compilation, tests, and CI validation.
SavigeSystemZGenerate conventional commit messages with EtherWeave scopes and types.