project-audit

Name: project-audit
Availability: InStock
Author: Fyodor

Analyze repositories to identify code-quality issues and generate prioritized TASKS.md.

Updated Aug 23, 2026

Search Tags:#audit #code-quality #static-analysis #code-review #dependency-management #task-generation

Ready to run

npx skills add https://github.com/fyodoriv/agentbrew --skill project-audit-fyodoriv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-audit
Source: https://github.com/fyodoriv/agentbrew/tree/main/skill-plugins/dev/project-audit
Command: npx skills add https://github.com/fyodoriv/agentbrew --skill project-audit-fyodoriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and prioritizes code-quality issues across an entire repository, helping teams catch bugs, dead code, missing error handling, stale docs, and outdated dependencies before they impact users.

Core Features & Use Cases

Repository-wide analysis of code quality and correctness across the whole project
Detects bugs, dead code, missing error handling, stale documentation, and outdated dependencies
Generates actionable TASKS.md entries with exact file paths and remediation steps for easy follow-through

Quick Start

Run the audit to surface code-quality issues and generate actionable TASKS.md entries.

Frequently Asked Questions about project-audit

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

FAQPage Schema

How do I identify and prioritize code-quality issues across my entire repository?▼

To identify and prioritize code-quality issues across a repository, you can run a code audit that analyzes the entire codebase to surface bugs, dead code, missing error handling, and outdated dependencies. It outputs a prioritized TASKS.md file with exact file paths and remediation steps for actionable follow-through.

Can I run a static code analysis on a project written in any programming language?▼

Yes, this code audit applies to any programming language and project size. It analyzes the repository to detect bugs, dead code, stale documentation, and outdated dependencies regardless of the tech stack.

How do I generate actionable tasks from stale documentation and dead code findings?▼

You can generate actionable tasks from dead code and stale documentation findings by running a repository audit. It outputs a TASKS.md file where each entry references concrete file paths, line numbers, and suggested remediation patterns consistent with the project's existing conventions.

What is the best way to detect outdated dependencies and missing error handling at scale?▼

The best way to detect outdated dependencies and missing error handling at scale is to perform a repository-wide audit. It analyzes the entire codebase to surface these specific code-quality issues and generates a prioritized list of actionable remediation steps.

Does a repository audit work for large codebases with mixed file types?▼

Yes, this repository audit is designed to work at scale across any project size. It analyzes the entire codebase to identify code-quality issues and outputs a prioritized TASKS.md containing exact file paths and line numbers for easy follow-through.