component-auditor
Skill192 starsChanged 6 days agoMITView on GitHub
Analyze existing components and inline sections for semantic duplication, style drift, and justified variants. Use for audit-only analysis, component-by-component alignment, or authorized reconstruction; preserve project-specific design and content decisions.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- component-builderSkill
- component-cleanupSkill
- component-inventorySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the audit and migration workflow.
- Distinctive: line 16
Update the existing component system document with decisions, consumer migrations, remaining gaps, and validation.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Component Auditor
Read the audit and migration workflow. Use a current project component system document; if missing or stale, establish the affected inventory before deciding. The inventory skill is optional convenience: this workflow defines the evidence needed without requiring another installed skill.
Choose the requested mode: audit-only, align-and-implement, or implement-confirmed. When the user wants discussion one component at a time, present evidence and proposed contract for that family before implementing undecided changes. Previously authorized decisions need no repeated approval.
Reuse project primitives and component contracts. Semantic responsibility, actual content and consumers determine consolidation, not naming or visual similarity. Keep content edits separate from behavior-equivalent migration. For host-specific copy in a stable shared component, use Pagina’s page-content-adapter.
Update the existing component system document with decisions, consumer migrations, remaining gaps, and validation. Publishing, pushing, and merging remain separate actions requiring task authorization.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.