cmd-pr-sweep

Analyze code diffs for test gaps, simplification, naming consistency, reuse, and TODO quality.

8|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Olshansk/agent-skills --skill cmd-pr-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmd-pr-sweep
Source: https://github.com/Olshansk/agent-skills/tree/main/skills/cmd-pr-sweep
Command: npx skills add https://github.com/Olshansk/agent-skills --skill cmd-pr-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, identifying potential issues across multiple dimensions to improve code quality and maintainability.

Core Features & Use Cases

  • Comprehensive Review: Analyzes code for test gaps, simplification opportunities, naming consistency, reuse potential, and TODO quality.
  • Actionable Feedback: Provides specific, actionable findings with file and line number references.
  • Use Case: Before merging a pull request, run this Skill to get a detailed report on potential test coverage issues, overly complex logic, or inconsistent naming conventions.

Quick Start

Run a code review sweep on your uncommitted changes.

Frequently Asked Questions about cmd-pr-sweep

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

FAQPage Schema
How do I automate code review for uncommitted git changes?

Automate code review for uncommitted git changes by running a multi-dimensional sweep that analyzes diffs for test gaps, simplification opportunities, naming consistency, and TODO quality. It provides actionable feedback with specific file and line number references.

What is the best way to find test coverage gaps in a git branch before merging?

The best way to find test coverage gaps in a git branch is to perform a targeted code review sweep. This analyzes branch diffs to identify missing tests and provides actionable feedback to improve code maintainability before merging.

How does a code review sweep identify refactoring and reuse opportunities?

A code review sweep identifies refactoring and reuse opportunities by analyzing code diffs to detect overly complex logic and naming inconsistencies. It evaluates changes against project-specific standards to recommend simplifications and reuse potential.

Do I need Git to analyze code diffs for maintainability issues?

Yes, you need Git to analyze code diffs for maintainability issues, as the review process requires Git for diff generation. It uses these diffs from uncommitted changes, branches, or specific files to provide actionable feedback.

Can I check TODO quality and naming consistency for specific files in my repository?

Yes, you can check TODO quality and naming consistency for specific files by targeting them in the code review sweep. The analysis evaluates the diffs from those files to provide targeted, actionable feedback on technical debt.

How do I review code changes for technical debt before a pull request?

Review code changes for technical debt before a pull request by running a multi-dimensional code review sweep. It identifies test gaps, complex logic, and inconsistent naming conventions, providing actionable feedback with file and line references to reduce maintainability issues.