Generates Conventional Commit messages from staged git diffs with heredoc commit commands.
npx skills add https://github.com/doccker/cc-use-exp --skill cc-commit-msg
Please help me install this Agent Skill. Skill: cc-commit-msg Source: https://github.com/doccker/cc-use-exp/tree/main/.codex/skills/cc-commit-msg Command: npx skills add https://github.com/doccker/cc-use-exp --skill cc-commit-msg
Writing consistent, well-structured git commit messages is repetitive and error-prone: subjects get overloaded, body bullets get flattened into one line by shell quoting, and mixed changes get crammed into a single commit. This Skill analyzes your staged diff and produces a properly formatted Conventional Commit message plus a copy-paste-ready heredoc command that preserves the subject/body structure.
git diff --cached by default (full working tree only when you explicitly say all), classifies the change intent as feat/fix/refactor/style/docs/test/chore, and warns when changes should be split into multiple commits.git commit -m "$(cat <<'EOF' ... EOF)" command so multi-line bodies survive shell parsing, and forbids broken \n single-line forms.fix: 修复列表接口分页读取错误 with body bullets and a ready-to-run heredoc command, then verify with git log -1.Generate a commit message for my currently staged changes and give me the heredoc git commit command to run.
High-intent search queries and answers about installing and using this skill.
Stage your changes with git add, then invoke the skill to analyze git diff --cached. It classifies the intent as feat, fix, refactor, style, docs, test, or chore and returns a subject line plus body bullets you can commit directly.
Use a heredoc: git commit -m "$(cat <<'EOF' ... EOF)" with the subject on the first line, a blank line, then body bullets. Single-quoted EOF prevents shell expansion, and the skill always outputs this form instead of broken \n single-line strings.
No. It only generates the message text and a copy-paste-ready heredoc command. It never executes git add or git commit on your behalf, and it is not a substitute for code review, release notes, or changelogs.
Yes, but only when you explicitly say all or request the full working tree. By default it inspects only the staged diff via git diff --cached; with the all flag it also reads git diff for unstaged changes.
The skill picks the dominant intent if one exists, otherwise it warns you to split the changes into separate commits. It avoids forcing mixed changes into a single feat message just to satisfy the type format.
GLaDO8Generates concise Git commit messages and commits staged or unstaged changes.
multigresGenerates a PR title and description from the branch diff and creates a draft pull request.
travelinman1013Automate pre-commit verification of staged code diffs with static scans, tests, and linting.
paloitmbbGenerate Conventional Commits messages and stage files for git commits.