Skip to content

Guide · Agent skill

How to use the GitHub Deep Review agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The GitHub Deep Review skill is an agent skill that makes an AI coding agent review GitHub issues and pull requests in depth, reading the code around a change instead of writing a generic summary. It is written for maintainers and engineers who have a local clone of the repository they are reviewing. After this guide you will know what the skill does, how to install it, how to ask for a review, and what to check before acting on its output.

GitHub Deep Reviewsteipete/agent-scripts · MIT

Quick start

  1. 1Download and unzip. Download the skill ZIP from this page and unzip the github-deep-review folder.
  2. 2Place the folder. Move it into ~/.claude/skills/ for personal use or into your project's .claude/skills/ folder for one repository, or upload it under Settings → Capabilities → Skills.
  3. 3Install prerequisites. Install and authenticate the GitHub CLI (gh), and make sure git and ripgrep (rg) are available.
  4. 4Clone the target repository. Have a local clone of the repository you want reviewed so the agent can read the code.
  5. 5Ask for a specific review. Name the issue or PR number and ask a concrete question such as root cause or best fix.
  6. 6Check the cited evidence. Open the files, symbols and tests the review cites and confirm them before acting.

What is an agent skill?

An agent skill is a folder containing a SKILL.md file with instructions that an AI agent loads when your request matches the skill's description. The skill tells the agent how to work on one kind of task, which tools to use and what to report.

This skill is one folder, github-deep-review, with a SKILL.md file and an agents/openai.yaml file.

What the skill makes the agent do

The skill asks the agent to use the GitHub CLI (gh), not web browsing, to pull issue and PR details, comments, reviews, changed files and diffs. It then reads the surrounding code in a local repository, following the real call path from entrypoint to the owning module, and checks git history for where a bug came from.

Every review is meant to answer a fixed set of questions: what the bug is, the root cause if it can be found, whether the proposed fix is the best one, whether a larger refactor would help, what proof exists, and what remains unverified. The skill tells the agent to say "not proven" when the evidence is weak.

  • Pulls issue and PR data with gh issue view and gh pr view, and diffs with gh pr diff.
  • Inspects local repo state with git status, git fetch origin and git log.
  • Searches the code for key symbols, errors, config or endpoints with rg.
  • For PRs, leads with findings that include file, line or symbol references and a concrete failure mode.
  • For regressions, separates the code author, introducing PR author, merger and current PR author, and labels provenance as clear, likely or unknown.

Install the skill

Download the ZIP for this skill from this page and unzip it. You can install it in one of two places.

For your user account, unzip it into ~/.claude/skills/ so the github-deep-review folder sits inside that directory. For a single project, unzip it into the project's .claude/skills/ folder instead.

In the Claude apps, you can upload the skill under Settings → Capabilities → Skills instead of copying files.

  • Personal install: ~/.claude/skills/github-deep-review/
  • Project install: <your-project>/.claude/skills/github-deep-review/
  • Claude apps: Settings → Capabilities → Skills
~/.claude/skills/github-deep-review/SKILL.md

Prepare your environment

The skill depends on several command-line tools. Install and check them before your first review. The skill expects gh to be authenticated to access the repository you are reviewing.

The skill also refers to a companion author-context skill at ~/Projects/agent-scripts/skills/github-author-context/SKILL.md. That file is not included in this download, so the author-context steps will not work as written unless you have it. Review work can still proceed without it.

  • GitHub CLI (gh), authenticated with access to the target repository
  • git
  • ripgrep (rg)
  • A local clone of the repository you want reviewed

Trigger the skill with natural requests

You do not need a special command. Describe the review you want in plain language and name the issue or PR number. Naming the local clone helps the agent find the code to read.

The skill is most useful when you ask for analysis rather than a summary. Ask about root cause, whether the fix is the best one, or whether the change introduced a regression.

  • Review PR 456 in this repo. Is the proposed fix the best one, and what proof exists?
  • Is issue 123 still a real bug on main, or was it already fixed?
  • Triage issue 123: find the root cause and tell me what evidence is missing.
  • Check when this regression was introduced and say unknown if the history does not prove it.

Read the output

Reviews follow a compact template. A PR review leads with findings and states whether there are blocking issues. If none are found, the output lists the strongest proof checked and the residual risk.

  • Ref and Surface: the issue or PR and the affected area.
  • Cause: code path and confidence.
  • Provenance: introduced, made visible or carried forward by a commit or PR, or N/A or unknown.
  • Best fix and Refactor: whether a larger change would help, and why.
  • Proof and Risk: tests, CI, source or docs checked, and what is still uncertain.

Safety notes: scripts and network

This skill runs scripts and uses the network. It calls gh to read GitHub data, and it runs git fetch origin, which contacts your remote. Check the commands before you approve them if your agent asks.

The skill tells the agent not to approve, comment, close, merge, push or land anything unless you explicitly ask. A misread of the output could still lead to a wrong decision, so have a human check the root cause and the proof before you act on it.

  • Read-only GitHub reads via gh; write actions are forbidden unless you ask.
  • git fetch origin updates your local repository from the remote.
  • The output may be wrong. Verify the cited files and tests yourself.

What people use it for

  • Triaging a bug report by reconstructing the scenario and checking whether current main already fixes it.
  • Reviewing a pull request for blocking correctness issues with file and symbol references.
  • Deciding whether a proposed fix is symptom-level or belongs at the ownership boundary.
  • Tracing when a regression was introduced using git log, git blame and linked PRs, with unknown reported when history cannot prove it.

Frequently asked questions

How do I install the github-deep-review skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder for one repository. You can also upload it in the Claude apps under Settings → Capabilities → Skills.

What do I need to run it?

You need the GitHub CLI (gh) authenticated to access the repository, git, ripgrep (rg), and a local clone of the target repository. The skill also refers to a companion author-context skill that is not included in these files.

Is the skill free to use?

The skill is published under the MIT licence. This page does not state pricing for the agent or any service it runs with, so check those separately.

Does the skill change anything on GitHub?

No. The skill forbids approving, commenting, closing, merging or pushing unless you ask for that action. It does run gh to read data and git fetch origin to update your local repository.

Can I use it on repositories other than the author's?

Not without adapting it. The skill references paths such as ~/Projects/agent-scripts and a companion author-context skill that is not included, and it is written around one maintainer's review style.

What should I use instead for a quick summary?

For quick summaries of issues or PRs, use a lighter tool. This skill is slow and token-heavy because it reads code deeply, so it suits triage and detailed review rather than fast overviews.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you maintain or review code in a repository you have locally and want evidence-based review notes with file references and an explicit list of unverified risks. Skip it for quick summaries, non-developer use, or repositories outside its author's ecosystem unless you are prepared to adapt it and check its conclusions yourself.

Download the skill