repo-audit

Audit a software repository and generate an ordered roadmap of epics.

1|2|Updated May 27, 2026
One-click install
npx skills add https://github.com/dividedby/skills --skill repo-audit-dividedby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-audit
Source: https://github.com/dividedby/skills/tree/main/skills/engineering/repo-audit
Command: npx skills add https://github.com/dividedby/skills --skill repo-audit-dividedby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of technical debt and backlog drift by identifying high-leverage architectural and performance improvements that are often overlooked in standard issue tracking.

Core Features & Use Cases

  • Blind Multi-Persona Audit: Uses a five-seat panel (Deletionist, Performance Analyst, Architect, Capability Scout, Convention Keeper) to hunt for improvements without bias.
  • Backlog Reconciliation: Ensures all findings are grounded against existing open issues, preventing duplicate work or ignored technical debt.
  • Roadmap Synthesis: Transforms raw findings into an ordered, epic-based roadmap with clear sequencing and dependency chains.

Quick Start

Invoke the repo-audit skill to perform a comprehensive leverage hunt across the current repository and generate an ordered roadmap of epics.

Frequently Asked Questions about repo-audit

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

FAQPage Schema
How do I audit a software repository for technical debt and architecture issues?

Auditing a software repository for technical debt involves running a multi-persona blind audit to hunt for high-leverage architectural, performance, and cleanup opportunities, then synthesizing findings into an ordered roadmap of epics.

What is the best way to prioritize a refactoring backlog against existing open issues?

The best way to prioritize a refactoring backlog is through backlog reconciliation, which grounds new architectural findings against existing open issues to prevent duplicate work and ensure technical debt is actionable.

How does a multi-persona blind audit work for codebase analysis?

A multi-persona blind audit works by deploying a five-seat panel, including a Deletionist, Performance Analyst, Architect, Capability Scout, and Convention Keeper, to independently hunt for improvements without bias.

Do I need an issue tracking system integration to generate a development roadmap?

Yes, integrating with your issue tracking system and repository configuration is required to ensure the synthesized epic-based roadmap is actionable and prioritized against your existing backlog.

Can I use this approach to identify performance improvements and cleanup opportunities?

Yes, you can identify performance improvements and cleanup opportunities by executing a leverage hunt across the repository, specifically targeting architectural bottlenecks and redundant code for deletion.

What are the limitations of using automated audits for technical debt management?

Automated audits are limited by their dependency on existing repository configurations and issue tracking integrations; without accurate backlog data, the synthesized roadmap may fail to prevent duplicate work or properly sequence dependencies.