skills.rest
julian-pani
julian-paniCOMMUNITY
Explore all skills by this author →
𝕏@JulianPaniGitHub

codebase-audit

Audit codebase health across quality, tests, documentation, and module organization.

2|Updated Jan 29, 2026
Search Tags:#documentation#refactoring#technical debt#test coverage#code audit#git history
One-click install
npx skills add https://github.com/julian-pani/agconf --skill codebase-audit-julian-pani
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-audit
Source: https://github.com/julian-pani/agconf/tree/main/.claude/skills/codebase-audit
Command: npx skills add https://github.com/julian-pani/agconf --skill codebase-audit-julian-pani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a manual, fragmented code review into a structured audit that highlights code quality issues, technical debt, documentation gaps, test coverage holes, and module organization problems.

Core Features & Use Cases

  • Comprehensive health assessment: Reviews the repository across quality, legacy code, tests, docs, and structure.
  • Commit-aware prioritization: Uses git history to focus attention on recently changed areas and likely hotspots.
  • Actionable consolidation: Produces prioritized reports and a unified remediation plan for follow-up work.
  • Use Case: Run it when onboarding to a new codebase, preparing a refactor, or checking whether a project is healthy enough for release work.

Quick Start

Ask the skill to audit the repository and include an optional commit range if you want the analysis focused on recent changes.

Frequently Asked Questions about codebase-audit

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

FAQPage Schema
How do I audit a codebase for technical debt and documentation gaps?▼

To audit a codebase for technical debt and documentation gaps, you can run a structured review that analyzes repository health across quality, tests, module organization, and legacy code to produce a consolidated remediation plan.

Can I prioritize code refactoring using git history and recent commits?▼

Yes, you can prioritize code refactoring by applying commit-aware analysis to git history, which focuses attention on recently changed areas and likely hotspots to guide your remediation efforts.

What is the best way to assess test coverage and module organization before a release?▼

The best way to assess test coverage and module organization before a release is to perform a comprehensive health assessment that reviews repository structure, legacy code, and test gaps to determine project readiness.

How do I check if a repository is healthy enough for release work?▼

You check repository health for release work by running a structured audit that evaluates code quality, technical debt, test coverage, and documentation gaps to produce an actionable remediation plan.

Does the codebase audit work with specific commit ranges?▼

Yes, the codebase audit works with specific commit ranges, allowing you to focus the analysis and parallel sub-agent reviews on recent changes rather than evaluating the entire repository history.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
dvy1987dvy1987
3

technical-debt-audit

Scan codebases for debt indicators and generate a prioritized remediation roadmap.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
verselesverseles
179

desloppify

Scan codebases across 28 languages for technical debt metrics.

Official
Advanced