Create Conventional Commits messages with type prefixes and descriptive bodies.
npx skills add https://github.com/milosptr/pos-system --skill commit-milosptr
Please help me install this Agent Skill. Skill: commit Source: https://github.com/milosptr/pos-system/tree/main/.claude/skills/commit Command: npx skills add https://github.com/milosptr/pos-system --skill commit-milosptr
Creating meaningful, consistently formatted commit messages that accurately describe changes to the codebase.
Stage relevant changes and create a well-formatted commit message using the Conventional Commits style.
High-intent search queries and answers about installing and using this skill.
To write conventional commit messages, apply standardized type prefixes like feat, fix, or refactor to your staged git changes, followed by a concise subject line and a detailed body describing the codebase modifications.
A conventional commit message requires a type prefix such as feat or chore, a concise subject line, an optional detailed body explaining the changes, and optional Co-Authored-By lines for proper attribution.
Yes, conventional commits standardize your version-control history with type prefixes, making the commit log suitable for automated release notes generation, code reviews, and maintaining clear audit trails across teams.
You need type prefixes in version control whenever you want a clean git history that clearly categorizes changes into features, fixes, refactors, or chores for better codebase maintenance and code review workflows.
The best way to format a git commit body for code reviews is to provide a detailed explanation of the changeset immediately after a concise subject line, ensuring reviewers understand the context and purpose of the modification.
jk278Analyze git repositories to summarize commit history and file changes.
ccfGenerate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.
cpfcoachingTeach structured git workflows including trunk-based development and atomic commits.
professor-moodyGenerate Git commit messages following the Conventional Commits specification.
