Ai-agent-skills module-audit-agent
Use when asked to audit a module, check its health, or assess whether it should be refactored. Runs structural query, risk check, and test generation automatically.
install
source · Clone the upstream repo
git clone https://github.com/wednesday-solutions/ai-agent-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/wednesday-solutions/ai-agent-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/agents/module-audit" ~/.claude/skills/wednesday-solutions-ai-agent-skills-module-audit-agent && rm -rf "$T"
manifest:
skills/agents/module-audit/SKILL.mdsource content
Module Audit Agent
When to use
- "Audit this module"
- "Is it safe to refactor X?"
- "What is the health of this service?"
- "Should we rewrite X?"
What to do
-
In parallel:
- brownfield-chat — Read
anddep-graph.json
for the target module. Report: what it does, its imports, what imports it, and any known conflicts.summaries.json - brownfield-fix — Run
andwednesday-skills score <module>
. Report risk band and total dependent count.wednesday-skills blast <module>
- brownfield-chat — Read
-
Present the combined audit report:
- Purpose summary (from summaries.json)
- Risk score + band (0–30 low / 31–60 medium / 61–80 high / 81–100 critical)
- Blast radius (dependent count, cross-language flagged separately)
- Architecture violations or danger zone warnings (from MASTER.md)
- Recommendation: proceed / review / senior sign-off / do not touch
-
brownfield-tests — Only run if coverage < 30% AND risk > 50:
- Run
wednesday-skills gen-tests --file <module> - Show generated test file to dev for review before writing
- Run
Never
- Recommend refactoring a critical file (risk > 80) without flagging the blast radius
- Read raw source to answer structural questions — use graph only
- Auto-write test files without showing the dev first