Generate Conventional Commits messages with type, scope, summary, and body.
npx skills add https://github.com/peerasak-u/pi-config --skill commit-peerasak-u
Please help me install this Agent Skill. Skill: commit Source: https://github.com/peerasak-u/pi-config/tree/main/skills/commit Command: npx skills add https://github.com/peerasak-u/pi-config --skill commit-peerasak-u
This Skill helps ensure commits follow the Conventional Commits format, delivering clear, consistent messages and improving traceability across a project.
Describe the change you made and run the commit helper to produce a conventional commit message.
High-intent search queries and answers about installing and using this skill.
To write a git commit using Conventional Commits format, describe your staged changes to generate a message with a type, optional scope, concise summary, and detailed body explaining what changed, why, and the approach.
The best way to structure a commit message for a bug fix is applying the Conventional Commits format, utilizing the fix type, a specific scope, and a descriptive body to clarify the resolution approach and impact.
You need to use a conventional commit format for version control when you want to standardize messaging across features, fixes, docs, and tests, ensuring clear traceability and easing changelog generation for the project.
This commit generation approach does not add breaking change markers or sign-offs, focusing solely on generating a polished type, optional scope, concise summary, and detailed body for typical code changes.
PedroHBOGenerates conventional commit messages and stages files from diffs.
marquesfelipAutomate semantic version bumps from conventional commits in CI/CD pipelines.
dtbuchholzStage Git changes, create conventional commits, push branches, and open pull requests via GitHub CLI.
shysssthanhtriGenerate Conventional Commit messages from staged Git diffs with Jira ticket IDs.
