Menu
Use when gathering compact GitHub pull request diff context, changed files, refs, commits, or a bounded diff for review/verification work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when managing per-project backlog folders, feature queues, async agent work items, lifecycle status updates, PR/done/blocked transitions, or status reviews inside an Obsidian vault.
Use when prototyping, authoring agent skills, or asking the agent to zoom out and map unfamiliar code before acting.
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
Use when reviewing architecture boundaries, hexagonal architecture, clean architecture layers, dependency direction, trust boundaries, uploads, parsers, redirects, or web security risks.
Use when configuring or running hexcheck in a Go repo for hexagonal architecture boundaries, adapter business-logic warnings, and mock discipline.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
| name | github-pr-diff-context |
| description | Use when gathering compact GitHub pull request diff context, changed files, refs, commits, or a bounded diff for review/verification work. |
Use this before reviewing or verifying PR feedback when you need a compact, reproducible view of what changed.
# Build step (one-time or when tools change):
tsc --project $HOME/.agents/skills/github/tools/tsconfig.json
# Then run:
node $HOME/.agents/skills/github/tools/dist/pr-diff-context.js --repo OWNER/REPO --pr PR_NUMBER --cwd /path/to/checkout
Defaults:
--repo from git origin--pr from gh pr view--cwd current directory/tmp artifacts with 0600 filesUseful options:
# Full JSON context on stdout
node $HOME/.agents/skills/github/tools/dist/pr-diff-context.js --repo OWNER/REPO --pr PR --stdout json
# Smaller or larger bounded diff
node $HOME/.agents/skills/github/tools/dist/pr-diff-context.js --repo OWNER/REPO --pr PR --max-diff-bytes 50000
Stdout summary includes:
truncated: true if the diff was intentionally size-limitedArtifacts:
truncated: true is not a GitHub data-completeness error; it only means the local diff text was clipped by --max-diff-bytes. Increase the limit if you need more context.
The tool uses gh pr view for PR metadata and local git diff base..head for diff text. If the local checkout does not have both SHAs, the metadata is still useful but the diff section may be empty with a warning.