Module Audit Agent Agent Skill
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
one command, takes just this skill from the repositorynpx skills add https://github.com/wednesday-solutions/ai-agent-skills --skill module-audit-agentThe instruction itself
4 sections, as written by the authorModule 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
dep-graph.jsonandsummaries.jsonfor the target module. Report: what it does, its imports, what imports it, and any known conflicts. - brownfield-fix — Run
wednesday-skills score <module>andwednesday-skills blast <module>. Report risk band and total dependent count.
- 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
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
Other skills for the same job
different authors, same section of the catalogue
Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state-of-the-art reasoning and coding.
Claude Skills meta-skill: extract domain material (docs/APIs/code/specs) into a reusable Skill (SKILL.md + references/scripts/assets), and refactor existing Skills for clarity, activation reliability, and quality gates.
> Pedantic backend pre-commit and atomic commit Skill for Django/Optimo-style repos. Enforces local AGENTS.md / CLAUDE.md, pre-commit hooks, .security/* helpers, and Monty’s backend engineering taste – with no AI signatures in commit messages.
Automatically backs up files, saves diffs, uses agents/skills, and ensures modular code (<200 lines) before any implementation. Use this skill for ALL code changes to ensure safe, reversible, and clean implementations.
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.
Configure human-in-the-loop gating for AI agent review actions in Claude Code. Use when setting up a project where an agent may post PR reviews, comments, merges, or edit CI configuration, and you want a cryptographically auditable approval trail with Cedar-enforced gates.
> Check installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.
How to use it
Take wednesday-solutions/module-audit-agent from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.