audit

Audit codebases for tech debt, quality, architecture, and dependency issues.

2|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/rioX432/live-translate --skill audit-riox432
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/rioX432/live-translate/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/rioX432/live-translate --skill audit-riox432

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly identify code quality, architecture, dependency, and UI issues in a repository and turn the findings into actionable GitHub issues.

Core Features & Use Cases

  • Static Analysis Coordination: Runs or triggers the project's lint and analysis commands to catch baseline failures early.
  • Parallel Code Scanning: Checks for tech debt, code quality problems, architecture boundary issues, visual defects, and dependency risks across the codebase.
  • Issue Triage and Filing: Deduplicates findings, assigns severity, and can create GitHub issues with labels and suggested fixes.
  • Use Case: A maintainer can audit a repo before a release to surface high-priority regressions, document them clearly, and queue them for the engineering backlog.

Quick Start

Ask the audit skill to review the repository scope you want, summarize the findings by severity, and create GitHub issues for the problems you want tracked.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit a codebase for tech debt and code quality issues?

To audit a codebase for tech debt and code quality issues, run the project's lint commands and perform parallel code scanning to catch baseline failures, architecture boundary violations, and dependency risks.

Can I automatically file GitHub issues for repository static analysis findings?

Yes, you can automatically file GitHub issues for repository static analysis findings. The audit process deduplicates findings, assigns severity labels, suggests fixes, and creates tracked GitHub issues for the engineering backlog.

How do I check for visual defects and UI issues in a repository?

You can check for visual defects and UI issues in a repository by running optional Playwright-based screenshot checks during the codebase audit to capture UI regressions and visual errors.

What is the best way to triage release readiness in a software repository?

The best way to triage release readiness is to perform a comprehensive codebase audit. This coordinates static analysis, parallel code scanning, and dependency review to surface high-priority regressions before release.

Does the codebase audit work with my existing lint commands and dependency setup?

Yes, the codebase audit works with your existing lint commands and dependency setup. It triggers your project's configured analysis commands to catch baseline failures and reviews dependency risks across the current environment.

What types of architecture boundary issues can a codebase audit detect?

A codebase audit detects architecture boundary issues through parallel code scanning. It identifies structural violations, tech debt accumulation, and dependency risks, then classifies their severity for GitHub issue creation.