sb-audit

Audit Storybook catalogs for naming drift and generate atomic JSON reports.

18|Updated Jun 16, 2026

Search Tags:#documentation #refactoring #drift detection #audit #component library #storybook

Ready to run

npx skills add https://github.com/strongeron/storybook-workbench --skill sb-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sb-audit
Source: https://github.com/strongeron/storybook-workbench/tree/main/skills/sb-audit
Command: npx skills add https://github.com/strongeron/storybook-workbench --skill sb-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of catalog fragmentation and naming drift in large Storybook projects, ensuring that your component documentation remains consistent, discoverable, and free of stale or unused code.

Core Features & Use Cases

Drift Detection: Automatically identifies inconsistent naming patterns across your story exports to help you consolidate your component library.
Lifecycle Management: Tracks the maturity of your stories, flagging deprecated or experimental code for pruning or graduation.
Usage Refresh: Synchronizes your Storybook documentation with the actual usage of components in your codebase, ensuring that prop-usage tables and design-system health metrics are always accurate.

Quick Start

Run the sb-audit skill to perform a full drift survey and refresh all rendered component usage documentation in your project.

Frequently Asked Questions about sb-audit

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

FAQPage Schema

How do I detect naming drift in a Storybook component library?▼

To detect naming drift in a Storybook component library, you can run an automated audit that analyzes story exports and component call-sites to identify inconsistent patterns and fragmented UI code for consolidation.

How do I find unused Storybook stories and manage their lifecycle?▼

You can find unused Storybook stories and manage their lifecycle by auditing story tags and component usage to flag deprecated or experimental code for pruning or graduation.

Do I need bash and python3 to perform a Storybook catalog audit?▼

Yes, you need bash and python3 installed in your environment to execute repository-wide scans and generate the atomic JSON reports required for the Storybook catalog audit.

What is the best way to refresh Storybook usage documentation?▼

The best way to refresh Storybook usage documentation is to synchronize your component documentation with actual codebase usage, ensuring prop-usage tables and health metrics remain accurate.

Can I generate JSON reports for Storybook integration from a component audit?▼

Yes, you can generate atomic JSON reports for Storybook integration by performing repository-wide scans that analyze component call-sites and story tags to output structured audit results.