Skip to content

System Audit — entry point

This skill is the invocation handle for the two-layer maintenance loop. The full architecture, mechanical/conceptual check lists, verbatim Layer 2 subagent prompt, output format, and constraints all live in the workflow doc — this file just routes you there.

When this fires

Auto-triggers on "audit", "check the system", "find issues", "repo health" — or explicit /audit. Designed for "leftover credits" use: 1–2× per day, find one improvement, fix it, done. Compounds without ever feeling like a project.

Begin

Read workflows/system_audit.md — authoritative spec. The "Orchestration sequence" section defines the 5 steps and contains the verbatim Layer 2 prompt to pass to the subagent. The "What each layer catches" tables enumerate the 10 mechanical and 10 conceptual categories.

Then execute Steps 1–5 from the workflow. Hard rule from the workflow: only ONE fix per invocation.

See also

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall