audit

Identify and rank code-quality issues against the Sublime anti-pattern catalog.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/nokusukun/sublime --skill audit-nokusukun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/nokusukun/sublime/tree/main/audit
Command: npx skills add https://github.com/nokusukun/sublime --skill audit-nokusukun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface and rank technical quality issues in code, mapping each finding to a defined anti-pattern in the Sublime catalog to guide safe improvements and reviews.

Core Features & Use Cases

  • Generate a prioritized punch list of defects, security risks, and anti-pattern hits tied to catalog entries.
  • Rank findings by severity (Dangerous, Wasteful, Cosmetic) to focus reviewer attention.
  • Provide actionable fixes with references to the governing anti-pattern sections for quick remediation guidance.

Quick Start

Run audit on a target file or directory to generate a prioritized punch list of findings.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I identify code quality issues before a merge?

To identify code quality issues before a merge, run an audit on the target directory to generate a prioritized punch list of defects, security risks, and anti-patterns. Findings are ranked by severity to focus reviewer attention on critical problems.

What is a code anti-pattern and how is it mapped during a review?

A code anti-pattern is a recurring design flaw that negatively impacts software quality. During a review, the audit maps each identified defect to a named anti-pattern in the Sublime catalog, providing a minimal fix reference to the governing section for remediation.

Can I use this audit skill for refactoring existing code?

Yes, you can use this audit skill for refactoring existing code. It supports typical review scenarios like refactors and PR reviews by surfacing technical quality issues and ranking them by severity to guide safe improvements.

What's the best way to prioritize security issues found in a codebase?

The best way to prioritize security issues is to rank findings by severity levels such as Dangerous, Wasteful, or Cosmetic. This categorization focuses reviewer attention on the most critical defects and anti-patterns first, ensuring dangerous vulnerabilities are addressed immediately.

Does the code review process provide guidance on how to fix identified defects?

Yes, the code review process provides actionable fixes with references to the governing anti-pattern sections. Each finding in the generated punch list is tied to a catalog entry, offering quick remediation guidance for developers.