# Github Deep Review

GitHub deep review: bugs, PRs, best fix, stale-or-real, read code first.

- Repository: https://github.com/steipete/agent-scripts (7431 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add steipete/agent-scripts --skill github-deep-review -g -a claude-code -y`
Codex: `npx skills add steipete/agent-scripts --skill github-deep-review -g -a codex -y`
Cursor: `npx skills add steipete/agent-scripts --skill github-deep-review -g -a cursor -y`
Gemini CLI: `npx skills add steipete/agent-scripts --skill github-deep-review -g -a gemini-cli -y`

## Description

GitHub deep review: bugs, PRs, best fix, stale-or-real, read code first.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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:

```bash
gh issue view <n> --json number,title,state,author,body,comments,labels,updatedAt,url
gh pr view <n> --json number,title,state,author,body,comments,reviews,files,commits,statusCheckRollup,mergeStateStatus,headRefName,headRepositoryOwner,url
gh pr diff <n> --patch
```

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:

```bash
git status --short --branch
git fetch origin
git log --oneline --decorate -20
rg "<key symbol/error/config/endpoint>"
```

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:

The rest: https://github.com/steipete/agent-scripts/blob/HEAD/skills/github-deep-review/SKILL.md