Agent skill · software engineering · abhigyanpatwari
gitnexus-review
Review code changes with GitNexus from a GitHub PR URL or number, a branch/ref or commit range, or local staged, unstaged, and untracked changes. Use when the user asks for a code review, merge-risk assessment, regression hunt, missing-test analysis, or a verdict on whether a PR, branch, commit range, or local diff is safe.
Why this skill is useful
Adds specific commands and workflows for reviewing code changes using GitNexus that the AI wouldn't reliably generate on its own.
What it needs
Requires gh, git installed locally. About 9k tokens when loaded. Last updated 2026-08-06. 45,147 stars on the source repository.
What this skill does
GitNexus review Review the requested change surface without editing source, committing, pushing, posting, or resolving threads. A later explicit request may authorize those actions. Use GitNexus for structural evidence and source inspection for proof; neither substitutes for the other. Resolve the target Accept these forms: Input Review surface ------------------------------------------------------ --------------------------------------------------------------------------- PR URL, owner/repo#42, #42, or bare number GitHub PR base...head Merge-base range base..head Exact two-dot range Branch, tag, or commit Ref against the repository default branch local, staged, unstaged, or working-tree wording Local changes No target Current branch's open PR; otherwise local changes; otherwise current branch An explicit target always wins. Interpret a bare number as a PR only in a GitHub repository with working gh authentication; otherwise ask for a ref or URL. If implicit mode finds both branch commits and local changes, review them as two labeled surfaces rather than silently dropping or blending either one. Record the resolved target kind, repository root, default branch, base SHA, head SHA, merge-base when applicable, and included local states. Resolve the default branch from remote metadata (refs/remotes/<remote>/HEAD or GitHub repository metadata); use main or master only as an explicit fallback and say when doing so. PR Use gh pr view/gh api to pin the PR number, repository, title, URL, base ref, base SHA, head ref, and head SHA. Fetch those exact commits without switching the user's branch. Compute git merge-base <base> <head> and use that SHA as the review base: GitHub PR diffs are merge-base diffs, while detectchanges(scope: "compare") is a two-dot comparison. Use the local git diff <merge-base> <head> as the complete diff source of truth; use GitHub metadata for PR facts and review state. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills abhigyanpatwari/gitnexus-review