skills.rest
wgordon17
wgordon17COMMUNITY
Explore all skills by this author →
GitHub

file-audit

Audit codebases to inventory symbols, dependencies, issues, and duplicates.

1|Updated Jan 13, 2026
Search Tags:#dependencies#audit#code-quality#duplication#drift#static-analysis#symbol-inventory
One-click install
npx skills add https://github.com/wgordon17/personal-claude-marketplace --skill file-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-audit
Source: https://github.com/wgordon17/personal-claude-marketplace/tree/main/code-quality/skills/file-audit
Command: npx skills add https://github.com/wgordon17/personal-claude-marketplace --skill file-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates thorough code-quality auditing to enumerate symbols, dependencies, issues, and potential duplicates across a codebase.

Core Features & Use Cases

  • Deep discovery across non-gitignored files to build a comprehensive inventory.
  • Parallel analysis with optional map-reduce for large projects to scale.
  • Drift detection against project memory (PROJECT.md, TODO.md, LESSONS.md) to surface documentation mismatches.

Quick Start

Audit your repository using /file-audit to generate an inventory and TODOs for your project.

Frequently Asked Questions about file-audit

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

FAQPage Schema
How do I perform a static analysis audit to find code duplication and symbol inventory across my project?▼

Perform a project-wide code audit by scanning all non-gitignored files to generate a structured inventory of symbols, dependencies, issues, and duplicates. This process surfaces duplicated code and builds a comprehensive symbol inventory for remediation planning.

What is code drift detection and how does it work with project documentation?▼

Code drift detection identifies mismatches between your implementation and project memory files like PROJECT.md, TODO.md, and LESSONS.md. It scans your codebase during the audit to surface discrepancies between documented goals and actual code behavior.

Can I audit a large codebase for dependencies and code quality issues without performance bottlenecks?▼

Yes, you can audit large codebases using optional parallelization and map-reduce techniques. This scales the static analysis across diverse projects by dividing the file scanning workload, ensuring comprehensive dependency and issue enumeration.

What's the best way to generate a compliance check inventory for my source code?▼

The best way to generate a compliance inventory is to run a deep code audit that exports a detailed per-file analysis alongside a consolidated symbol and dependency listing. This structured output is specifically suitable for governance and compliance checks.

Does the code quality audit work with any programming language or framework?▼

The audit applies to diverse codebases by scanning all non-gitignored files regardless of language. It enumerates symbols and dependencies universally, making it suitable for varied technical stacks without requiring specific framework configurations.

Related Skills

Explore More Software Engineering Skills→
giovannimnzgiovannimnz

gsd-new-project

Initialize a new project by generating a planning scaffold with PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md.

Community
Advanced
ribatsheporibatshepo
1

spec-compliance

Parse Markdown, YAML, or JSON specs and generate a compliance matrix with evidence.

Community
Advanced
rysweetrysweet
1

simplify

Review changed code via git diffs and apply fixes for reuse, quality, and efficiency.

Community
Advanced
yonyon
3

lint

Run linters and static analysis tools with severity-based output and auto-fix mode.

Community
Basic