audit

Run repository-wide tech-debt audits and consolidate severity-ranked findings.

22|3|Updated Jul 28, 2024
One-click install
npx skills add https://github.com/webdevcody/go-mailing-list --skill audit-webdevcody
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/webdevcody/go-mailing-list/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/webdevcody/go-mailing-list --skill audit-webdevcody

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you find and remove accumulated tech debt across an entire repository by running a broad set of targeted code-audit checks, consolidating their results, and applying safe, mechanical fixes while gating higher-risk structural changes.

Core Features & Use Cases

  • Whole-repo tech-debt sweep: Orchestrates multiple audit/check skills (simplification, duplication detection, type hardening, data integrity, error boundaries, loading states, contracts, observability, performance, security regression, concurrency, client bundle, and accessibility) against the agreed scope.
  • Severity-ranked consolidation: Merges overlapping findings from multiple audits into one deduplicated, severity- and category-organized report for clear prioritization.
  • Safe application workflow: Applies formatter/lint and low-risk mechanical fixes automatically, then gates structural and behavior-adjacent refactors (including test/verification steps) to keep the diff bisectable and production readiness high.
  • Run-mode and scope controls: Supports mode selection (fast/balanced/production), caller-provided skip lists, and scope narrowing to avoid noisy audits.

Quick Start

Tell the AI to audit the codebase with a production-grade hardening pass and apply mechanical fixes.

Frequently Asked Questions about audit

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

FAQPage Schema
What is the best way to run a production-readiness code audit?

A full codebase audit consolidates overlapping findings from multiple checks into one severity-ranked, category-organized report, deduplicating results so you can clearly prioritize type hardening, security regressions, and performance improvements.

How do I scope a code audit to avoid noisy results in large repositories?

You can automatically apply mechanical fixes like formatter and lint corrections during a code audit, but structural and behavior-adjacent refactors are gated behind user confirmation and test verification steps to keep diffs bisectable.

What limitations exist when using an automated tool for tech debt refactoring?

You can scope a code audit by using caller-provided skip lists and narrowing the audit scope, which prevents noisy results and allows you to target specific areas for production-readiness passes or hardening efforts.

How do I consolidate overlapping findings from multiple code audit checks?

Automated tech debt refactoring limits changes to mechanical fixes like formatting and linting, explicitly gating higher-risk structural and behavior-adjacent refactors to ensure the codebase maintains high production readiness and bisectable diffs.