One-click install
npx skills add https://github.com/wednesday-solutions/ai-agent-skills --skill module-audit-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: module-audit-agent
Source: https://github.com/wednesday-solutions/ai-agent-skills/tree/main/skills/agents/module-audit
Command: npx skills add https://github.com/wednesday-solutions/ai-agent-skills --skill module-audit-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you audit a module’s health and refactor risk without hallucinating architecture or missing hidden blast impacts.

Core Features & Use Cases

  • Parallel module understanding: Summarizes what the module does and which imports/conflicts are involved using structural artifacts.
  • Risk and blast-radius assessment: Computes a risk score and dependent impact using structural scoring and dependency queries.
  • Coverage-aware test generation: Generates tests only when coverage is low and risk is high, and shows them for dev review before writing.

Quick Start

Ask an AI to run the module audit by requesting: "Audit this module and decide whether we can refactor it safely, including blast radius, risk band, and recommendations."

Frequently Asked Questions about module-audit-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a module's health and refactor safety before making code changes?

To audit a module's refactor safety, run parallel queries against precomputed structural context to assess its health, calculate risk scores, and evaluate blast radius. This determines whether a service can be refactored safely without missing hidden impacts.

What is blast radius analysis and how does it assess refactor risk?

Blast radius analysis assesses refactor risk by computing a risk score and dependent impact using structural scoring and dependency graph queries. It identifies hidden architectural impacts to determine safe change windows.

Can I generate tests automatically when auditing module architecture violations?

Yes, you can generate tests during a module audit, but only when coverage is low and risk is high. Generated tests are displayed for developer review before any test file is written to ensure safe integration.

Does this module audit approach require any specific dependencies or external tools?

No, this module audit approach requires no external dependencies. It operates independently using precomputed structural artifacts to summarize module functionality, identify import conflicts, and calculate risk band classifications.

When should I avoid using automated risk scoring for code refactoring?

You should avoid automated risk scoring when precomputed structural context is unavailable. Without accurate dependency graphs and architecture violation data, blast radius assessments cannot reliably detect hidden refactor impacts.