skills.rest
Durwood-Studios
Durwood-StudiosOFFICIAL
Explore all skills by this author →
GitHub

super-audit

Audit codebases read-only and report issues with file:line evidence.

Updated Apr 8, 2026
Search Tags:#code audit#deep investigation#codebase review#read-only audit#file:line evidence
One-click install
npx skills add https://github.com/Durwood-Studios/Dura --skill super-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: super-audit
Source: https://github.com/Durwood-Studios/Dura/tree/main/.claude/dura-claude-skills/super-audit
Command: npx skills add https://github.com/Durwood-Studios/Dura --skill super-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a comprehensive, read-only audit of a codebase, identifying issues, gaps, and potential risks with detailed file:line evidence.

Core Features & Use Cases

  • Deep Audit: Synthesizes eleven investigation lenses into one report.
  • Read-Only: Never edits files, only produces a report.
  • File:Line Evidence: Every claim is backed by file path and line number.
  • Use Case: Before a launch or marketing rollout, to ensure the codebase meets standards and expectations.

Quick Start

Run the super-audit skill on your codebase to generate a detailed report.

Frequently Asked Questions about super-audit

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

FAQPage Schema
How do I conduct a read-only codebase audit before a launch?▼

A read-only codebase audit analyzes your code without modifying files, identifying issues, gaps, and risks. It synthesizes eleven investigation lenses into a single report, backing every claim with file path and line number evidence for pre-launch verification.

Can I get file:line evidence for issues found during a code review?▼

Yes, a deep code review can provide file:line evidence for every identified issue. This ensures that all claims regarding codebase risks, gaps, and compliance are precisely traceable to specific locations in your source files.

Do I need Claude Code with grep and bash access for a deep codebase investigation?▼

Yes, conducting a deep codebase investigation requires Claude Code with grep, view, and bash read access. These tools allow the audit to systematically search and read your files to generate a comprehensive risk report.

What is the best way to check codebase compliance without modifying files?▼

The best way to check compliance without modifying files is a read-only audit. It evaluates your codebase against standards and expectations, producing a detailed report of potential risks and issues without ever editing your source code.

Are there limitations to running an automated code audit on my repository?▼

An automated code audit is limited to read-only operations and does not fix the issues it finds. It requires specific tool access like grep and bash to function, and its output is strictly an investigative report with file:line evidence.

Related Skills

Explore More Software Engineering Skills→
sncollectivesncollective

scan-quality

Identify code duplication, complexity, and pattern drift in a codebase.

Official
Intermediate
flavien-iaflavien-ia
34

security

Audit Next.js and T3 stack applications for security vulnerabilities across twelve categories.

Community
Advanced
prof-danielcprof-danielc

speckit.checker

Run static analysis tools and aggregate results into a prioritized issue report.

Community
Advanced
steadyfallsteadyfall

qa-only

Generate a report-only QA assessment with health score and repro steps for web applications.

Community
Intermediate