Menu
Create a well-formed git commit from the current changes. Use when finalizing staged work, preparing a commit message, or splitting in-progress work into reviewable history.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | symphony-commit |
| description | Create a well-formed git commit from the current changes. Use when finalizing staged work, preparing a commit message, or splitting in-progress work into reviewable history. |
git log --oneline -20 first; conventional-commit prefixes are common but the leading-identifier style — SYM-31: etc. — also appears).--no-verify. If a hook fails, fix the underlying problem and create a new commit.git status, git diff, git diff --staged for actual changes.origin/main for style.git status, git diff, git diff --staged.git add <paths>). Avoid git add -A / git add . — they sweep in .env, credentials, large binaries, or artifacts you didn't mean to ship..symphony-workspace-ready, and locally injected fallback skills under .agents/skills/symphony-* or .claude/skills must stay unstaged unless the issue explicitly asks to install or change Symphony skills. Exception: .symphony/screenshots/<name>.png is intentionally staged only by the symphony-screenshot skill's temporary evidence commit (which also --no-verifys, the only place that's allowed); that skill then creates a cleanup revert commit so the files do not remain in the latest tree while the evidence commit remains in branch history.<TYPE>(<scope>): <summary> or <IDENTIFIER>: <summary>.git commit -F <file> (or the heredoc form) so newlines are real, not literal \n.<type>(<scope>): <short imperative summary>
<one-paragraph rationale: why this change, what it unblocks, any tradeoff>
- <key change 1>
- <key change 2>
git commit -m "$(printf 'a\nb')" — it's brittle. Use a heredoc.--no-verify, --no-gpg-sign). If a hook fails, fix the cause.Sync the current branch with origin/main via merge (not rebase) and resolve any conflicts. Use whenever Symphony's workflow says "merge origin/main into the branch" — at Step 1 setup, before push, and as part of the Land procedure.
Push the current branch to origin and ensure a PR exists for it (creating or updating one), with the symphony label applied. Use when the workflow says "push" or "open a PR".
Sync the current branch with origin/main via merge (not rebase) and resolve any conflicts. Use whenever Symphony's workflow says "merge origin/main into the branch" — at Step 1 setup, before push, and as part of the Land procedure.
Push the current branch to origin and ensure a PR exists for it (creating or updating one), with the symphony label applied. Use when the workflow says "push" or "open a PR".
Squash-merge the issue's PR once it's approved and green. Use only when the issue is in the `Merging` state — Symphony's status router gates entry.
Sweep the PR for actionable reviewer feedback (top-level comments, inline review comments, review states) and resolve every item before moving to In Review. Use after every push that might have triggered review, and as the gate before transitioning the issue to In Review.