Repository navigation
v0.3.0
What you can do with v0.3.0
Make an existing repository safe for AI coding agents, with two skills for Claude Code.
- Clone this repository and start Claude Code in it.
- Say: "Audit /path/to/your/repo and write the output to /path/to/output". You get an evidence-cited readiness
report. The audit never writes inside your repository. - Say: "Start implementing the fixes on /path/to/your/repo based on /path/to/output/.json". The skill fixes
the confirmed findings one theme at a time, on local branches. It never merges.
No clone wanted? Download the two skill zips below, check them with SHA256SUMS, and unzip them into your project's
.claude/skills/ folder: install the skills.
What changed since v0.2.0
- One layout:
docs/,spec/,greenfield/,audit/,implement/,dev/. Old paths are listed in the
"Moved" table ofCHANGELOG.md. - The skills start from a clone with no install step.
- Inside the audit bundle the engine moved to
scripts/engine/audit/. Unzip the new release over the old folders. - Each bundle now carries its licence (AGPL-3.0-or-later).
SECURITY.md, a protectedmain, and secret scanning are in place.
Platforms
Linux: tested. macOS: the tools are tested in CI; the Claude Code path is not yet checked by hand. Windows: not
tested (WSL may work).
Files
| File | What it is |
|---|---|
agentic-readiness-audit-v0.3.0.zip |
The audit skill |
agentic-readiness-implement-v0.3.0.zip |
The implement skill (install beside the audit skill) |
audit.pyz |
The deterministic engine as one file: python3 audit.pyz --help |
SHA256SUMS |
Check the downloads: sha256sum -c SHA256SUMS |
Full notes: CHANGELOG.md.