Menú
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".
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
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.
| name | push |
| description | 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". |
gh auth status succeeds.commit skill first).pnpm format:check && pnpm lint && pnpm typecheck && pnpm test).branch=$(git branch --show-current).git push -u origin HEAD
pull skill to merge origin/main, re-run validation, then push again. Use --force-with-lease only when you knowingly rewrote history; never use --force.pr_state=$(gh pr view --json state -q .state 2>/dev/null || true)
gh pr create --title "<title>" --body "<body>".OPEN → gh pr edit --title "<title>" --body "<body>" if scope shifted.CLOSED/MERGED → branch is non-reusable; cut a fresh branch from origin/main.SYM-NN: <summary>.symphony label via REST (the gh pr edit --add-label path 500s on this org due to a Projects-classic GraphQL deprecation):
pr_number=$(gh pr view --json number -q .number)
repo=$(gh repo view --json nameWithOwner -q .nameWithOwner)
gh api -X POST "repos/${repo}/issues/${pr_number}/labels" -f 'labels[]=symphony'
gh pr view --json url -q .url.git push usually creates a Linear attachment automatically; if not, fall back to GraphQL attachmentLinkURL (or attachmentLinkGitHubPR for GitHub-specific link metadata).gh pr merge --squash --auto).