Agent skill · writing content · steipete
github-deep-review
GitHub deep review: bugs, PRs, best fix, stale-or-real, read code first.
Why this skill is useful
Provides specific workflows and commands for conducting thorough code reviews that the AI wouldn't reliably generate on its own.
What it needs
Requires gh, ripgrep installed locally. About 4k tokens when loaded. Last updated 2026-08-06. 6,510 stars on the source repository.
What this skill does
GitHub Deep Review Review like Peter: high-confidence, evidence-first, code-aware, and willing to say "not proven" when the trail is weak. The goal is not a generic summary. The goal is to understand the bug class, find the real cause if possible, decide the best fix after reading enough code, and call out whether a larger refactor would improve the design. Start Use gh, not web browsing, for GitHub refs: For PRs, collect author context by default unless the author is Peter (steipete or an obvious Peter-owned account). Use the local workflow in ~/Projects/agent-scripts/skills/github-author-context/SKILL.md and include a short Author context: block near the top of the review when the author is not Peter. After merge/rejection/close/review, use that same author-context workflow to append a contributor note only when the interaction creates durable future-review signal. For repo-local review, also inspect: If the repo has local instructions, issue/PR skills, docs lists, test guidance, or maintainer runbooks, read those before deciding. Review Contract Always answer these, explicitly: URL/ref: issue or PR number and affected surface. What is the bug or behavior being fixed? Can we identify the root cause? If yes, where in code and why. If no, what evidence is missing. For regressions, who/what introduced it and when? Include commit/PR provenance when traceable by bounded history; say unknown instead of guessing. Is the current/proposed fix the best possible fix after reading adjacent code? Would a bigger refactor improve correctness, clarity, or future maintainability? What proof exists: tests, live repro, CI checks, docs, dependency docs/source, shipped/current behavior. What remains risky or unverified. Code Reading Depth Read past the first touched file. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/github-deep-review