gitnexus-review

Reviews GitHub PRs, branches, commit ranges, and local diffs using GitNexus graph evidence.

1|Updated Jul 27, 2023
One-click install
npx skills add https://github.com/AlexTheGuitarGuy/.dotfiles --skill gitnexus-review-alextheguitarguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-review
Source: https://github.com/AlexTheGuitarGuy/.dotfiles/tree/main/claude/.claude/skills/gitnexus-review
Command: npx skills add https://github.com/AlexTheGuitarGuy/.dotfiles --skill gitnexus-review-alextheguitarguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss regressions that live outside the diff — broken dependents, removed sanitizers, stale baselines, and untested behavior changes. This Skill performs evidence-backed reviews of PRs, branches, commit ranges, or local changes by combining the raw git diff with GitNexus dependency-graph, impact, and taint analysis. ## Core Features & Use Cases - Flexible target resolution: Accepts a PR URL or number, a branch/ref, a base...head or A..B range, or local staged/unstaged/untracked changes, resolving each to exact base and head SHAs. - Graph-backed impact analysis: Runs detect_changes, impact, context, and PDG-based taint passes to find broken dependents, source-to-sink flows, and missing test coverage. - Expert lens and swarm lanes: Dispatches domain-specific reviewer lenses plus six read-only CI personas (correctness, security, blast radius, coverage, adversarial, critic) for multi-domain changes. - Use Case: Ask for a review of PR #42; the Skill pins the merge-base, diffs it against the head in a temporary worktree, traces every behaviorally changed symbol's dependents, and returns a severity-ordered findings list with an APPROVE or REQUEST CHANGES verdict. ## Quick Start Review the changes in PR #42 of this repository and tell me whether it is safe to merge.

Frequently Asked Questions about gitnexus-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a GitHub PR with GitNexus?▼

Provide a PR URL, owner/repo#number, or bare PR number and the review resolves the base and head SHAs, computes the merge-base, and diffs it locally. It then runs GitNexus impact and taint analysis on changed symbols and returns severity-ordered findings with a verdict.

What code changes can this review skill analyze?▼

It accepts GitHub PRs, branches, tags, commits, two-dot and three-dot ranges, and local staged, unstaged, and untracked changes. With no target given, it reviews the current branch's open PR, otherwise local changes, otherwise the current branch.

Does the review modify my working tree or post comments?▼

No. The review is strictly read-only: it uses a temporary detached worktree at the target SHA and never switches, resets, commits, pushes, or posts. Those actions require a later explicit request.

Why does the review use merge-base instead of the default branch tip?▼

GitHub PR diffs are merge-base diffs, so comparing against a moving default branch tip would include unrelated changes. The review computes git merge-base of base and head and uses that SHA as the comparison base for both the diff and detect_changes.

What are the limitations of graph-based code review?▼

Graph results can miss new files, dynamic dispatch, reflection, configuration, and untracked content, so the review reconciles graph evidence with the raw diff. If an exact checkout or fresh index cannot be built, the review states the limitation instead of claiming full graph-backed coverage.