md-audit

Scans a codebase for bugs, dead code, and security hotspots and returns a prioritized findings report.

1|Updated Aug 23, 2026
One-click install
npx skills add https://github.com/foxmaster77/12BOT --skill md-audit-foxmaster77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: md-audit
Source: https://github.com/foxmaster77/12BOT/tree/main/munder-difflin-main/munder-difflin-main/resources/skills/md-audit
Command: npx skills add https://github.com/foxmaster77/12BOT --skill md-audit-foxmaster77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate hidden issues like hard-coded secrets, unhandled errors, and dead code that are easy to miss during day-to-day development. This Skill performs a read-only audit of the current working directory and delivers a severity-ranked findings report without modifying any files. ## Core Features & Use Cases - Read-Only Scanning: Uses Grep and Read to inspect code without editing a single file, making it safe to run on any repository. - Targeted Issue Detection: Looks for unhandled promise rejections, hard-coded credentials, TODO/FIXME/HACK debt markers, dead exports, and type-safety gaps. - Prioritized Report: Outputs findings sorted by severity (Critical, High, Medium, Low) with file and line references plus a summary count. - Use Case: Before a release, ask for a quick audit of your project to surface a leaked API key in a config file and several ignored error handlers, all listed with exact file locations. ## Quick Start Ask the assistant to audit the code in the current working directory and report any issues it finds.

Frequently Asked Questions about md-audit

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

FAQPage Schema
How do I audit my codebase for security issues?▼

Run a read-only code audit that greps the working directory for hard-coded secrets, tokens, and passwords, plus unhandled errors and type-safety gaps. Findings are returned as a report sorted by severity from Critical to Low with file and line references.

How to find dead code and unused exports in a project?▼

Dead code detection works by identifying exported symbols that have no corresponding import anywhere in the repository. The audit flags these dead exports alongside TODO, FIXME, and HACK comments that signal known technical debt.

Does a read-only code audit modify my files?▼

No, a read-only audit only uses Read, Grep, and Bash to inspect files and never edits anything. It stops after producing the findings report and does not apply any fixes.

What languages does a code audit scan support?▼

The audit identifies the primary language by looking for manifest files such as package.json, Cargo.toml, go.mod, or pyproject.toml. It then scopes its scan to the detected project's entry points and source files.

What are the limitations of a grep-based code audit?▼

A grep-based audit relies on pattern matching, so it can miss context-dependent bugs and may produce false positives on secrets or dead code. It is best used as a fast first-pass scan rather than a replacement for deep static analysis or manual review.