agentsclimarketplace

Module audit

Skill wednesday-solutions/ai-agent-skills/skills/agents/module-audit

Pre-configured agent skills for Vibe Coded projects. These skills provide AI coding assistants (Claude Code, Cursor, etc.) with specific guidelines for code quality and design standards.

Install
npx -y skills add wednesday-solutions/ai-agent-skills --skill module-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, as published. Nobody here has run it

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

  1. In parallel:

    • brownfield-chat — Read dep-graph.json and summaries.json for the target module. Report: what it does, its imports, what imports it, and any known conflicts.
    • brownfield-fix — Run wednesday-skills score <module> and wednesday-skills blast <module>. Report risk band and total dependent count.
  2. 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
  3. 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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.