codebase-auditor

Name: codebase-auditor
Availability: InStock
Author: keystone-ui

Audit Keystone UI component source and story files for convention violations.

3|Updated Feb 24, 2026

Search Tags:#performance #react #component library #design tokens #code audit #animation #documentation review

Ready to run

npx skills add https://github.com/keystone-ui/react --skill codebase-auditor-keystone-ui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codebase-auditor
Source: https://github.com/keystone-ui/react/tree/main/.cursor/skills/codebase-auditor
Command: npx skills add https://github.com/keystone-ui/react --skill codebase-auditor-keystone-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you review the Keystone UI codebase for architectural, styling, documentation, performance, and animation drift so issues are caught before release.

Core Features & Use Cases

Reviews component source files against project rules and conventions.
Checks story files for documentation quality, variant coverage, and interaction tests.
Produces a severity-ranked report with concrete fixes for release readiness and refactor follow-up.

Quick Start

Ask the skill to audit the codebase or a specific component and return a structured report of violations and fixes.

Frequently Asked Questions about codebase-auditor

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

FAQPage Schema

How do I audit a React component library for convention violations before release?▼

Auditing a React component library involves validating component source files against project conventions, checking story files for variant coverage, and producing a severity-ranked report with concrete fixes for release readiness.

What does a codebase drift check cover for React performance and animation patterns?▼

A codebase drift check covers React performance optimizations, animation patterns, architecture, and design tokens, catching actionable quality issues and convention violations before release.

How do I review React story files for documentation quality and variant coverage?▼

Reviewing React story files requires checking documentation quality, variant coverage, and interaction tests, ensuring alignment with repository rules during full or focused component audits.

Can I run a focused component review instead of a full codebase audit?▼

Yes, you can run a focused component review or a post-refactor check instead of a full audit, targeting specific component source and story files to validate architecture and performance.

What is the best way to find design token violations in a UI codebase?▼

The best way to find design token violations is to audit the codebase against project conventions, validating token usage and producing a severity-ranked report with concrete fixes for any drift.