reuse-audit

Detect existing composables and utilities in the webkit monorepo.

2|5|Updated Oct 24, 2023

Search Tags:#code reuse #component scaffolding #vue composables #duplicate logic detection #design system utilities #static code search

Ready to run

npx skills add https://github.com/aziontech/webkit --skill reuse-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reuse-audit
Source: https://github.com/aziontech/webkit/tree/main/.claude/skills/reuse-audit
Command: npx skills add https://github.com/aziontech/webkit --skill reuse-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents duplicated composables, utility components, and same-category siblings by scanning the codebase before you scaffold a new component.

Core Features & Use Cases

Index existing reusables by enumerating composables and matching utilities/siblings to capture export names and component identifiers.
Match by intent using spec-driven needs (props/events/states) such as loading/spinner, toast/notification, dialog open/close, currency/price, and tags.
Emit structured reuse suggestions as a JSON array so the scaffolding step can recommend real existing implementations or return an empty result.

Quick Start

Use the reuse-audit skill in component creation to scan the spec and return a JSON array of existing utilities that satisfy the component’s needed logic.

Frequently Asked Questions about reuse-audit

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

FAQPage Schema

How do I find existing Vue composables before scaffolding a new component?▼

To find existing Vue composables before scaffolding, use a static code search to index package paths. It matches component specs against existing utilities to prevent code reuse duplication.

What is the best way to prevent duplicate logic detection in a monorepo?▼

The best way to prevent duplicate logic detection is scanning the monorepo via intent-based keyword matching. This matches props, events, and states to existing same-category siblings before implementation.

How do I match component spec needs like loading states to existing utilities?▼

You match component spec needs by applying intent-based keyword matching against indexed composables. This maps required states like loading or toast to existing design system utilities.

Can I use component scaffolding workflows with read-only filesystem indexing?▼

Yes, component scaffolding workflows use read-only filesystem indexing of specific package paths. This safely enumerates existing reusables and matches them without modifying the codebase.

Does duplicate logic detection output structured data for automated scaffolding?▼

Yes, duplicate logic detection emits a structured JSON array of reuse paths. This output resolves to real files, allowing automated component scaffolding to recommend existing implementations directly.

What limitations exist when scanning for reusable UI logic across packages?▼

A key limitation is that reuse path suggestions must resolve to real files under specific package paths. If matching utilities exist outside these indexed directories, they will not be detected.