skillshare-codebase-audit
FeaturedCross-validate CLI flags, docs, tests, and targets for consistency across the codebase. Use this skill whenever the user asks to: audit the codebase, check for consistency issues, find undocumented flags, verify test coverage, validate targets.yaml, check handler split conventions, or verify oplog instrumentation. This is a read-only audit — it reports issues but never modifies files. Use after large refactors, before releases, or whenever you suspect docs/code/tests have drifted out of sync.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- runkids
- Repository
- runkids/skillshare
- Created
- 8 months ago
- Last Updated
- today
- Language
- Go
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
skill-audit
Consistency audit of one skill's instruction files: builds the load graph, then finds contradictions between SKILL.md and its supporting files, directives no load path reaches, and stale pointers (renamed paths, skills, flags, headings). A fresh-context reader writes the report; a second pass re-verifies each finding and fixes what is clear. Use for "/skill-audit <skill>", "audit this skill", or when a skill that has been edited many times starts behaving inconsistently. Not for writing a new skill or making one known fix.
skill-auditor
Audit the skills library for duplicates, stale content, spec violations, and structural issues. Run periodically or before releases.
skill-auditor
Audit an Agent Skill or a repository of skills for trigger quality, scope overlap, instruction conflicts, progressive-disclosure cost, broken references/dependencies, eval blind spots, false-green paths, semantic-version and public-contract compatibility, host-support overclaims, package hygiene, supply-chain risks, migration/deprecation gaps, and drift between registry, docs, tests, and shipped archives. Use when the user asks to audit, review, roast, harden, compare, or quality-check a skill or skill library itself. Do not use to create/edit the skill (use skill-creator), to empirically benchmark model behavior with-vs-without it (use skill-evaluator), to audit ordinary software (use repo-roaster), or to issue a production release verdict.