Create a well-formed git commit from current changes using conversation history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/symphony-agent-skills:commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Produce a commit that reflects the actual code changes and the conversation
git status, git diff, and git diff --staged for actual changes.git status, git diff,
git diff --staged).git add -A) after confirming
scope.feat(scope): ..., fix(scope): ..., refactor(scope): ...).Co-authored-by trailer using
Co-Authored-By: Claude <[email protected]> unless the user explicitly
requests a different identity.git commit -F <file> so newlines are literal (avoid -m with \n).git commit whose message reflects the
conversation.Type and scope are examples only; adjust to fit the repo and changes.
<type>(<scope>): <short summary>
Summary:
- <what changed>
- <what changed>
Rationale:
- <why>
- <why>
Tests:
- <command or "not run (reason)">
Co-Authored-By: Claude <[email protected]>
npx claudepluginhub markoinla/symphony --plugin symphony-agent-skillsStages intended git changes avoiding secrets and creates clear Conventional Commits like feat(scope): subject. Useful for clean, semantic commit history.
Creates conventional commit messages for staged git changes following the Conventional Commits spec and VGV workflow. Stages unstaged files interactively when needed.
Drafts Conventional Commits messages for staged git changes. Proposes a type-scoped subject line, waits for user approval, then commits.