Generate Git commit messages following the Conventional Commits specification.
npx skills add https://github.com/sergical/pi-config --skill commit-sergical
Please help me install this Agent Skill. Skill: commit Source: https://github.com/sergical/pi-config/tree/main/skills/commit Command: npx skills add https://github.com/sergical/pi-config --skill commit-sergical
This Skill ensures that all Git commits adhere to the Conventional Commits standard, resulting in clear, descriptive, and consistent commit messages that improve project history and automation.
feat(api): Implement user authentication endpoint with a detailed explanation of the changes.Use the commit skill to create a commit with the message "feat: Add new user profile page".
High-intent search queries and answers about installing and using this skill.
Conventional commits structure Git commit messages by enforcing a format with a type, optional scope, concise summary, and a detailed body. This standardizes project history and enables automation.
To generate a conventional commit message, use this skill to process your staged changes. It formats the output with the appropriate type, scope, and a detailed body explaining the what and why of your code modifications.
Yes, this skill supports adding a scope and detailed body to Git commit messages. It generates informative commit bodies and applies scopes, formatting commits as feat(api): Implement user authentication endpoint.
You should use the conventional commits specification for version control history because it ensures clear, descriptive, and consistent commit messages. This improves project readability and supports automated semantic versioning and changelog generation.
The best way to format a feature commit for a new API endpoint is using the conventional commits standard. This skill generates a structured message like feat(api): Implement user authentication endpoint, complete with a detailed explanation.
lvndryGenerate conventional commit messages from git diffs and context.
Sharper-FlowAutomate release lifecycle with semver versioning and GitHub releases.
lihaoze123Run spec compliance, linting, type-checking, and testing before commits.
storm-softwareGenerate conventional commit messages for staged Git changes.