Menü
Merge the current branch's PR after confirmation
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
| name | pr-merge |
| description | Merge the current branch's PR after confirmation |
Use this skill when the user asks to run the migrated command pr-merge or invokes $pr-merge.
Merge the GitHub PR for the current branch. This is the ONLY authorized path to merge a PR.
gh pr view --json number,url,title,state,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup \
--jq '{number, url, title, state, mergeable, mergeStateStatus, reviewDecision, checks: [.statusCheckRollup[]? | {name: .name, status: .status, conclusion: .conclusion}]}'
If no PR exists, stop: "No open PR found for branch $(git branch --show-current)."
Report any blockers:
If there are blockers, report them and stop. Do not proceed.
Present the PR summary and ask for confirmation:
PR #<number>: <title>
CI: ✅ all passing (or ❌ N failing)
Reviews: ✅ approved (or ⚠️ pending / ❌ changes requested)
Conflicts: none (or ⚠️ has conflicts)
Merge method?
Use AskUserQuestion to let the user pick the merge method:
gh pr merge <number> --<method> --delete-branch
Where <method> is squash, rebase, or merge based on the user's choice.
✅ Merged PR #<number> via <method>
<pr_url>
Branch deleted: <branch>
git checkout main && git pull --prune
The --prune flag removes local remote-tracking refs for branches deleted on the remote (including the just-merged branch).
End-of-day — draft and post daily comments for tracked tickets missing a comment
Morning startup workflow for daily notes, yesterday summary, agenda, status comments, meeting sections, and daily branch setup. Use when invoked as `$work-start` or when the user asks to start the work day.
Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track` or when the user asks to track a work item.
Start work on a Linear ticket by gathering context, planning, creating a branch/worktree, implementing, testing, opening a draft PR, and updating Linear. Use when invoked as `$linear-plan` or when the user asks to start a Linear ticket.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.