Format git commit messages with a Conventional Commits-style subject.
npx skills add https://github.com/mpsuesser/workspace --skill commit-mpsuesser
Please help me install this Agent Skill. Skill: commit Source: https://github.com/mpsuesser/workspace/tree/main/dotconfig/pi/agent/skills/commit Command: npx skills add https://github.com/mpsuesser/workspace --skill commit-mpsuesser
It helps you format your git commit messages clearly and consistently so your project history stays readable and searchable.
<type>(<scope>): <summary> format with a concise, imperative summary.Review your git status and git diff, then create a Conventional Commits-style commit message for the intended changes (for example: feat(ui): improve settings page layout).
High-intent search queries and answers about installing and using this skill.
A conventional commit message follows the `<type>(<scope>): <summary>` structure, keeping the imperative summary concise and under 72 characters without trailing periods. Optional structured bodies can be added for additional context.
The conventional commits subject line requires a type, an optional scope in parentheses, and a concise summary. This structure improves repository clarity and ensures project history stays readable across features, fixes, chores, or refactors.
Review your `git status` and `git diff` to stage only the intended files. If file inclusion is ambiguous, the workflow prompts for clarification to ensure you commit exactly the intended code changes consistently.
You can add an optional structured body to your conventional commit for extra context. However, breaking-change markers and sign-offs are discouraged to keep the version control history clean and focused.
Yes, the conventional commits format applies directly to local git workflows. It helps you format commit messages clearly and consistently across features, fixes, chores, or refactors without needing external dependencies.
Using a conventional commit format instead of free text keeps your repository history readable and searchable. Enforcing a structured `<type>(<scope>): <summary>` syntax ensures consistent code changes documentation across your project.
faustellar1995Analyze staged git changes to draft commit messages.
ccfGenerate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.
CodySwannGTCreate conventional commits and submit pull requests for code review.
kreuzberg-devEnforce Conventional Commits and pre-commit hooks for formatting, linting, and tests.