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".
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
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".
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.
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.
| name | symphony-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, and plain git push has credentials for the repo host.
If relying on GitHub CLI for HTTPS git credentials, run gh auth setup-git first
(gh auth setup-git --hostname <host> for a non-default host). GITHUB_TOKEN/GH_TOKEN
alone can authenticate gh pr ... commands but is not enough for git push -u origin HEAD.symphony-commit skill first).pnpm verify:full).branch=$(git branch --show-current).git push -u origin HEAD
symphony-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).