mxa-audit-code
Assesses the health of an inherited codebase before anything is built on it: what tests exist, what they cover according to the repository's own reports, whether they run before deployment, where the flaky and untested areas are, and how much is duplicated, dead or circular where the ecosystem's own tools are installed. It executes no tests.
- Reads the tree for a real test command, a lockfile and CI that runs the tests, in JavaScript, Ruby or Python.
- Quotes coverage only as the repository's own report states it, with its date, and never measures it itself.
- Finds the marks flakiness leaves: focused tests, skipped tests, fixed sleeps and retries.
- Measures duplication, dead code, circular imports and complexity with the ecosystem's own tools where they are installed, and leaves the dimension out where they are not.
- Is the natural first act on a client's codebase, alongside the security audit.
What is inside
The checks module reads a JavaScript, Ruby or Python tree for its test command, lockfile, CI wiring, coverage reports and flakiness markers, and drives jscpd, knip, madge and rubocop for quality where they are installed. It executes no tests.
- Uses
- jscpdknipmadgerubocop
- Evals
- 3
Works with
The outside tools and connectors this skill drives.
- Reads the codebase directly· our default
- jscpd, knip and madge on JavaScript
- rubocop on Ruby
- a project's own code-health tooling
The first is what we reach for on our own projects. A project that already uses one of the others keeps it, and the skill works with that instead.