Menü
Sync the current branch with the latest base branch (PR base if a PR exists, otherwise origin/main).
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
Merge an approved PR during the Land state. Runs pre-flight checks, performs squash merge, completes post-merge bookkeeping, and transitions the issue to Done.
Manage GitHub Project v2 issue states, workpad comments, and related follow-up actions.
Analyze backlog issues to set Priority, Size, and Estimate, then identify and connect blocking relationships between issues. Use when backlog items need evaluation or when new items have been added without triage.
Manage a repository's GitHub Project workflow through PROJECT_MANAGE.md. Use when setting up project management for a repo, creating structured issues from implementation requests, triaging backlog items with Priority/Size/Estimate, analyzing blocking relationships across open issues, or rendering a project status dashboard.
Design, refine, and validate repository WORKFLOW.md files for GitHub Symphony projects.
Initialize PROJECT_MANAGE.md with repository-specific project management rules, GitHub Project board binding, and field mappings. Use when setting up project management for a repository for the first time.
| name | pull |
| description | Sync the current branch with the latest base branch (PR base if a PR exists, otherwise origin/main). |
| license | MIT |
| metadata | {"author":"gh-symphony","version":"2.0","generatedBy":"gh-symphony"} |
Use this skill to bring the current branch up to date with its base branch:
/land skill's pre-flight check 3 (branch up-to-date with PR base) fails.Determine the base branch:
# If a PR exists for the current branch:
pr_number=$(gh pr view --json number --jq .number 2>/dev/null)
if [ -n "$pr_number" ]; then
base=$(gh pr view --json baseRefName --jq .baseRefName)
else
base="main"
fi
Fetch latest:
git fetch origin "$base"
Rebase the current branch onto the base:
git rebase "origin/$base"
rebase (not merge) keeps the branch history linear and avoids creating merge commits — required for the squash-merge policy used by /land.If conflicts arise:
git rebase --continue after staging the resolution.After a successful rebase, the local branch has new commit SHAs. If the branch was already pushed (e.g. a Draft PR exists), force-push with lease:
git push --force-with-lease origin <branch-name>
--force-with-lease is safer than --force: it refuses to overwrite if the remote moved since your last fetch.
Record the pull skill evidence in the workpad ### Validation section:
origin/feature/epic-x or origin/main)clean or conflicts resolvedgit rev-parse --short HEADorigin/main) when a PR exists. An Epic working branch must rebase against the Epic base, not main.git rebase (not git merge) to keep history linear for the squash-merge policy.