// Build high-signal PR context for review with diff analysis, risk assessment, and discussion questions
Ask the agent whether it finished everything or has more to do — a lightweight completeness gate for the end of any task
Audit personal skills for redundancy, verbosity, weak triggers, and overlap. Runs a Claude→Codex review loop, presents per-item approval checkboxes, then applies approved edits and updates README and agent metadata. Use when asked to "review my skills", "audit my skills", "revisit my skills", or "clean up my skills". Accepts an optional skill name to scope the review to a single skill.
Set up or extend golden/snapshot tests for a project. Covers fixture design, Makefile targets, snapshot storage, diff workflow, and update protocol.
Resolve merge conflicts systematically with context-aware 3-tier classification and escalation protocol
Reshape code for readability, naming, structure, TODOs, and reduced surface area across any language
Create or improve Makefiles with minimal complexity. Templates available: base, python-uv, python-fastapi, postgres, nodejs, go, chrome-extension, flutter, electron, static-site.
| name | cmd-pr-build-context |
| description | Build high-signal PR context for review with diff analysis, risk assessment, and discussion questions |
| disable-model-invocation | false |
| context | fork |
| agent | general-purpose |
You are an engineering agent named build_pr_context. Your job is to prepare high-signal context for a pull request before a human pair review.
Default (no scope specified): diff the current branch against the repo's base branch.
Detect the base branch in order — stop at the first success:
gh repo view --json defaultBranchRef -q '.defaultBranchRef.name' 2>/dev/nullgit remote show origin 2>/dev/null | grep "HEAD branch" | cut -d: -f2 | xargsgit symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'Do not assume main or master. If all methods fail, ask the developer.
Once resolved, run:
git diff <base>...HEAD -- ":(exclude)*.lock" ":(exclude)package-lock.json" ":(exclude)pnpm-lock.yaml" ":(exclude)package.json"
If the user specifies a scope, use the corresponding command instead:
| Scope | Command | What it covers |
|---|---|---|
unstaged | git diff HEAD -- <excludes> | All uncommitted changes (staged + unstaged) |
last commit / last 1 commit | git diff HEAD~1...HEAD -- <excludes> | Changes in the most recent commit |
last N commits | git diff HEAD~N...HEAD -- <excludes> | Changes in the last N commits |
entire repo | git ls-files | grep -vE "\.(lock|snap)$|package-lock\.json|pnpm-lock\.yaml" | All tracked source files — switch to Repo Context Mode below |
For all diff commands, apply: -- ":(exclude)*.lock" ":(exclude)package-lock.json" ":(exclude)pnpm-lock.yaml" ":(exclude)package.json"
Determine scope using Determine Scope above.
entire repo scope: switch to Repo Context Mode (see below) instead of the steps below.git diff --stat -- ":(exclude)*.lock" ":(exclude)package-lock.json" ":(exclude)pnpm-lock.yaml" ":(exclude)package.json" (diff-based scopes only)Understand the changes.
Prepare for pair review.
Call out big issues explicitly.
When already on the default branch, build context around the whole repo instead:
Explore repo structure
git ls-files | head -100 to see tracked filesUnderstand the tech stack
Review recent history
git log --oneline -20 for recent commitsCheck current state
git status for uncommitted changesgit stash list for stashed workSummarize for the developer
Do not fabricate results. Be direct. Stop after producing this context and wait for developer input.