codebase-sweep

Discover and prioritize codebase quality issues into a findings document.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Maxcogar/agent-armory --skill codebase-sweep-maxcogar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-sweep
Source: https://github.com/Maxcogar/agent-armory/tree/main/claude-plugins/agentboard/skills/codebase-sweep
Command: npx skills add https://github.com/Maxcogar/agent-armory --skill codebase-sweep-maxcogar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically discover every quality issue in a codebase through a single broad sweep, then organize findings into a prioritized document.

Core Features & Use Cases

  • Discover and triage quality issues across the codebase without performing fixes.
  • Produce a prioritized findings document to guide refactoring, debt resolution, and improvement planning.
  • Suitable for audits of messy projects, architecture reviews, and pre-migration readiness.

Quick Start

Initiate a codebase sweep on your project to produce a prioritized findings document.

Frequently Asked Questions about codebase-sweep

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

FAQPage Schema
How do I audit a codebase to identify technical debt across different architectures?

To audit a codebase and identify technical debt, you can run a single broad sweep across multiple languages and architectures. This systematically discovers quality issues and outputs a prioritized findings document for triage.

What is the best way to discover and triage code quality issues in a messy project?

The best way to discover and triage code quality issues in a messy project is a comprehensive codebase sweep. It systematically surfaces all quality problems and organizes them into a structured, prioritized document for refactoring.

Can I use a codebase sweep to fix code issues or enforce architecture during the review?

A codebase sweep cannot fix code issues, enforce architecture, or run linters. It strictly performs discovery and triage of quality issues, outputting a structured findings document rather than applying automated fixes.

How do I prepare a messy codebase for refactoring and migration readiness?

To prepare a messy codebase for refactoring and migration readiness, perform a broad sweep to surface technical debt. This generates a prioritized findings document that guides subsequent resolution and improvement planning.

Does a codebase sweep replace automated linting tools for code review?

A codebase sweep does not replace automated linting tools, as it does not run linters or perform fixes. Instead, it systematically audits the codebase to surface technical debt and produces a prioritized document to guide manual code reviews.