review-changes

Solid

Review branch changes or a PR for code quality, tests, documentation, and commit hygiene. Routes to the `review-loop` skill for a bounded review-apply-simplify convergence loop, or to `pr-reviewer` directly for a one-shot read-only review. Invoke with /review-changes.

Code & Development 13 stars 2 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
38
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

## Routing Choose the path based on the argument shape: | Argument shape | Path | Reason | | --- | --- | --- | | no arg / `--report` | `Skill("review-loop", "<pr-url> [--critical\|--no-ci\|--external-review\|--interval S]")` on the current branch's open PR, or `pr-reviewer` directly if `--report` (one-shot, no apply) | Own PR convergence loop, or one-shot report. | | PR URL or `#<n>` | `Skill("review-loop", "<pr-url> [--critical\|--no-ci\|--external-review\|--interval S]")` — runs the bounded review-apply-simplify loop | Converges the PR regardless of who authored it (`pr-reviewer` detects `REVIEW_RELATION` itself). | `--no-ci`, `--external-review` and `--interval S` are pass-throughs: this skill never sets them itself, it only forwards what the user passed (see the note below). ```bash # --report routes straight to pr-reviewer, which --external-review exists to avoid. # Refuse the pair rather than accepting a flag this path cannot honour, mirroring # review-loop's refusal of --no-feedback --external-review. case "$ARGUMENTS" in *--report*) case "$ARGUMENTS" in *--external-review*) echo "--report needs pr-reviewer; drop --external-review or drop --report." exit 1 ;; esac ;; esac # Resolve the current branch's PR whenever no PR was named. Test for the ABSENCE of a # PR reference, never for an exact flag string: every flag in the table above is # combinable, so `= "--report"` left `--external-review`, `--critical`, `--no-ci`, and # `--interval S` with n...

Details

Author
mthines
Repository
mthines/agent-skills
Created
4 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

review

Review PRs and repo health with one skill, three modes. Default: recap the session's goal, discover every PR it opened, and review/merge each in dependency order. Given PR number(s): a deep sub-agent review (not the author) with file:line grounding, an architecture rubric (reuse, cross-cutting-at-source, no duplicate surfaces, doc-asserted invariants), and a security pass on risk-touching diffs. Given `repo` / a path / `--since <date>`: a read-only whole-repo architecture-and-quality diagnostic (four orthogonal categories, HTML report, no merge verdict). Triggers on: 'review the PR', 'code review', 'review #N', 'before I merge', 'block this PR', 'security review', 'what's wrong with this branch', 'health check', 'parallel implementations', 'audit drift'.

0 Updated today
phnx-labs
Code & Development Solid

review-loop

Bounded review-apply-resolve convergence loop for a GitHub PR (draft PRs are fine). Runs up to N=5 iterations of pr-reviewer → implement-suggestion (--resolve-all) → polish simplify, converging until every review thread is resolved — through a fix OR a reply (answered question, recorded rationale) — so the PR is left with zero open threads (only genuine human-judgment flags stay open). On convergence it also refreshes the PR description to match the shipped diff and, best-effort, notes the linked Linear ticket. Use after opening a draft PR to converge the branch to a clean, review-ready state before undrafting. Also converges CI: after each iteration's push it reads the check state and delegates a red mechanical failure to ci-auto-fix, so convergence means zero open threads AND CI not red (--no-ci opts out; create-pr and autonomous-workflow pass it because they own their own CI phase). On a UI PR it also runs the committed preview-spec block against the live preview deployment once at exit (report-only, never

13 Updated yesterday
mthines
Code & Development Listed

pr-review

Reviews a branch, PR, staged, or working-tree diff for correctness, security, repo-convention, test-coverage, and documentation gaps, returning severity-rated findings without editing code. Use when asked to "review my branch/PR", "is this ready to merge", "check this diff before I push", "does this need an ADR", or to apply fixes for findings from a previous review round. When the target is a GitHub PR, the same report is also posted to the PR — as inline comments on each finding's line plus a summary, by default — so the whole team can read it.

3 Updated today
eagerworks