audit

Audit codebases for quality, security, architecture, performance, dependency, and process issues.

10|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/fiftynotai/igris-ai --skill audit-fiftynotai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/fiftynotai/igris-ai/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/fiftynotai/igris-ai --skill audit-fiftynotai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and organizes codebase issues across quality, security, architecture, performance, dependencies, and process so teams can prioritize and track remediation without modifying source code.

Core Features & Use Cases

  • Multi-type Audits: Run targeted audits for code_quality, bugs, standards, process, dependencies, performance, and architecture or run a full combined audit.
  • Actionable Findings: Reports include file:line locations, severity, suggested fixes, and recommended brief types for tracked remediation.
  • Brief Creation: Automatically recommends and creates briefs for critical findings to feed into the project's brief-first workflow and backlog.
  • Use Case: Run a dependency and security audit across a monorepo to generate DU-XXX briefs for outdated or vulnerable packages and TD-XXX briefs for technical debt introduced by deprecated APIs.

Quick Start

Ask the audit skill to run a full audit across the repository and generate briefs for critical findings.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I run a code quality and security audit on my repository?

Run a full code audit by applying the skill across your repository to detect quality, security, and performance issues. It generates file:line findings with severity categorizations and suggested fixes without modifying source code.

What is the best way to audit technical debt and outdated dependencies in a monorepo?

Auditing technical debt and dependencies in a monorepo requires running targeted dependency and process audits. This identifies vulnerable packages and deprecated APIs, generating recommended brief types like DU-XXX and TD-XXX for tracked remediation.

Can I audit specific code directories instead of running a full repository scan?

Yes, you can audit specific code directories instead of a full repository scan. Apply the skill to selected directories to run targeted audits for code_quality, bugs, standards, performance, or architecture modules independently.

How does an architecture audit identify issues in a codebase?

An architecture audit identifies codebase issues by analyzing structural design flaws and technical debt. It generates file:line findings, categorizes severity, suggests fixes, and recommends brief types suitable for creating tracked remediation briefs.

Does the code audit tool automatically fix detected security and performance issues?

No, the code audit tool does not automatically fix detected security and performance issues. It organizes findings with suggested fixes and recommended brief types, allowing teams to prioritize and track remediation without altering source code.