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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Capture Playwright screenshots of a user-facing change and embed them in the GitHub PR description via a temporary commit + force-push. Use whenever the workflow asks for proof-of-testing screenshots on a user-facing change.
Manage the single Symphony Workpad comment on a Linear issue — find or bootstrap, update in place, or reset (Rework). Use whenever the workflow needs to read or write the workpad. Includes the GraphQL `commentUpdate` workaround for the known Linear MCP `save_comment` duplication bug.
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.
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".
| name | 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 must stay unstaged. Exception: .symphony/screenshots/<name>.png is intentionally staged by the screenshot skill's throwaway commit (which also --no-verifys, the only place that's allowed) and is removed by the same skill's force-push step.<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.