full-systems-audit

Audit a codebase end to end and produce a routed findings backlog with stable IDs.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/Lawrence908/chiron --skill full-systems-audit-lawrence908
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-systems-audit
Source: https://github.com/Lawrence908/chiron/tree/main/plugins/dev/skills/full-systems-audit
Command: npx skills add https://github.com/Lawrence908/chiron --skill full-systems-audit-lawrence908

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or unfamiliar codebases accumulate architectural drift, god modules, misleading names, and hidden tech debt that no single review can surface. This Skill maps the entire system and converts findings into a durable, citable backlog instead of a one-off report. ## Core Features & Use Cases - End-to-end mapping: Builds a file manifest, dependency graph, flow traces, and a control-deck inventory of configs, env vars, and external state. - Surface integrity checks: Audits exported functions, CLI flags, API routes, and log/event strings for name-vs-behavior mismatches, near-duplicate pairs, and doc drift. - Routed backlog with stable IDs: Every finding gets a permanent ID, severity, blast radius, and a lane (plan-first, single-pr, or defer) that downstream plans and PRs can cite. - Use Case: Before a major refactor, run the audit to get audit-report.md and audit-backlog.md, then triage each item by fixing it, deferring it, or handing it to a supporting skill like python-refactor. ## Quick Start Audit this repository end to end and produce an audit report plus a routed backlog of findings with stable IDs.

Frequently Asked Questions about full-systems-audit

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

FAQPage Schema
How do I audit a codebase for architecture and tech debt?▼

Run a phased audit: build a file manifest and dependency graph, trace critical flows, inventory configs and env vars, then synthesize findings by severity. Each finding gets evidence, a stable ID, and a routing lane so later work can cite it directly.

What should a codebase audit report include?▼

A useful audit report contains a system summary, architecture notes, a control-deck assessment of configs, findings grouped by severity with file:line evidence, and an honest note on what is healthy. Pair it with a routed backlog so findings become actionable work items.

When should I not run a full systems audit?▼

Skip it when hunting functional bugs, reviewing a single pull request, evaluating visual surfaces, or working on code about to be deleted or rewritten. Those cases call for targeted bug hunts, code review, or visual QA instead of a full mapping exercise.

How do I detect misleading function and API names in a codebase?▼

Compare each exported name against its actual behavior, check near-duplicate pairs like create/new/init or remove/delete/clear for accurate contrast, and verify docstrings match current implementations. Naming inversions on load-bearing surfaces rate as high-severity findings.

Why do audit findings need stable IDs?▼

Stable IDs let downstream plans, pull requests, and commits cite findings verbatim without ambiguity. Items are never renumbered or silently dropped; when work lands or is invalidated, the status changes to fixed, superseded, or deferred while the ID persists.