review-sweep

Scan open GitHub PRs and GitLab MRs to triage unresolved reviewer threads.

Updated May 20, 2026

Search Tags:#code review #GitHub #pull requests #triage #merge requests #GitLab #CI repair

One-click install

npx skills add https://github.com/semanticpixel/abc --skill review-sweep

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: review-sweep
Source: https://github.com/semanticpixel/abc/tree/main/plugins/abc/skills/review-sweep
Command: npx skills add https://github.com/semanticpixel/abc --skill review-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the time you spend repeatedly checking review feedback by scanning all your open PRs and MRs and organizing unresolved reviewer threads into actionable batches.

Core Features & Use Cases

Bulk PR/MR reviewer triage across GitHub & GitLab: enumerates your authored open PRs/MRs, pulls unresolved reviewer threads, and identifies what can be fixed versus what needs judgment.
Safety-first guided fixing: proposes fixes for fixable threads, gates auto-application behind explicit confirmation, and avoids resolving threads without a fix.
Health pre-pass and CI red-handling: attempts mechanical rebase repairs and one-shot production-only CI repair (without touching test paths), then surfaces escalations clearly in a dashboard.

Quick Start

Run the skill to scan your open PRs and MRs for unresolved reviewer threads and generate a dashboard of fixable items versus judgment-required decisions for you to apply.

Frequently Asked Questions about review-sweep

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

FAQPage Schema

How do I triage unresolved code review comments across multiple GitHub pull requests and GitLab merge requests at once?▼

To triage unresolved code review comments in bulk, this skill scans all your open GitHub PRs and GitLab MRs, categorizing unresolved reviewer threads into fixable items and judgment-required decisions. It outputs an aggregated dashboard for quick action.

Can I automatically fix code review feedback from GitLab merge requests without manual editing?▼

You can automatically address fixable merge request feedback using safety-guarded fixes applied after an explicit user confirmation gate. The system proposes fixes per merge request and avoids resolving threads without applying a valid repair.

What is the best way to handle failing CI checks on open pull requests while resolving reviewer threads?▼

Handling failing CI checks alongside reviewer threads involves running health pre-passes that attempt mechanical auto-rebases and one-shot production-code CI repairs with strict test-path and anti-cheat constraints, escalating issues if repairs fail.

Does this automated PR triage tool require separate authentication for GitHub and GitLab repositories?▼

Automated PR triage requires GitHub and GitLab authentication preflights to access your open pull requests and merge requests. These preflights validate your credentials before the tool enumerates your authored open items for thread scanning.

What limitations exist when applying automated CI repair to pull request code?▼

Automated CI repair limitations include a strict one-shot attempt constraint for production-only code, prohibiting any modifications to test paths, and enforcing anti-cheat constraints to prevent superficial fixes from bypassing failing checks.