audit-review

Verify PR review findings, sweep defect classes, and resolve review threads before merge.

33|12|Updated Sep 24, 2024
One-click install
npx skills add https://github.com/bgaldino/rlm-base-dev --skill audit-review-bgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-review
Source: https://github.com/bgaldino/rlm-base-dev/tree/main/.cursor/skills/audit-review
Command: npx skills add https://github.com/bgaldino/rlm-base-dev --skill audit-review-bgaldino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated PR reviewers (Codex, Copilot) generate findings that are sometimes wrong, duplicated, or only partially fixed, and branches merging to main risk silently reverting newer main-side changes. This Skill provides a disciplined playbook for verifying each finding against the actual code, sweeping entire defect classes instead of patching single lines, and closing every review thread before merge. ## Core Features & Use Cases - Finding triage and verification: Classify each bot comment as real, partial, or false-positive with evidence, then sweep the whole class across the feature rather than fixing only the cited line. - Thread resolution protocol: Reply in-thread with the resolution and commit SHA, react to valid comments, and resolve threads via GraphQL until zero unresolved threads remain. - Pre-merge main comparison audit: Detect branch-side reverts of main content, foreign or stacked commits from composed integration branches, and overlapping file changes using git diff, merge-base, and the check_branch_scope.py script. - Use Case: Before merging a long-running feature branch into a release branch, run the branch-scope check, triage all Copilot and Codex comments into defect classes, fix every instance of each class, and close the round with zero unresolved threads. ## Quick Start Ask the agent to process all open review comments on the current pull request using the audit-review skill, verifying each finding, sweeping its class, and resolving every thread.

Frequently Asked Questions about audit-review

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

FAQPage Schema
How do I handle automated PR review comments from Copilot or Codex?

Verify each comment against the actual code and classify it as real, partial, or false-positive. Fix every instance of a valid finding's class, reply in-thread with the commit SHA, react to valid comments, and resolve the thread via GraphQL.

How do I resolve GitHub review threads with the API?

GitHub's REST API cannot resolve review threads; use the GraphQL resolveReviewThread mutation with the thread ID. List threads with the reviewThreads query under repository pullRequest, paginating with endCursor until hasNextPage is false.

How do I check if a branch contains commits it does not own?

Run python scripts/ai/check_branch_scope.py with --pr before merging. It reports FOREIGN findings for content already upstream via git cherry patch-id matching, and STACKED findings for branches built on another open PR's head.

Why does a clean merge-base diff still hide reverted main changes?

When a branch is rebased onto main's tip, the merge-base equals main's tip, so the overlap intersection is empty even if branch commits reverted inherited main content. Detect this by diffing the branch against main directly and ranking files by deletions.

When should I not trust an automated review finding?

Never take a bot finding at face value; bots are sometimes wrong, such as false claims about getMap() key casing. Read the cited source, reproduce the claim, and refute false positives with evidence while still resolving the thread.