Claude-skill-registry auditing-project
Audits the project for consistency issues that may arise from manual editing. Checks package scripts, tsconfig paths, README tables, and other conventions.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/auditing-project" ~/.claude/skills/majiayu000-claude-skill-registry-auditing-project && rm -rf "$T"
manifest:
skills/data/auditing-project/SKILL.mdsource content
Auditing Project
Check for inconsistencies that may have been introduced by manual editing.
Steps
Run each audit script with
--check- Package scripts:
.claude/skills/authoring-global-scripts/scripts/sync-package-scripts.ts --check - TSConfig paths:
.claude/skills/syncing-tsconfig-paths/scripts/sync-tsconfig-paths.ts --check
If issues are found, run the corresponding skill to fix them.
Reference
What Gets Checked
| Check | Detects |
|---|---|
| Package scripts | Scripts out of sync with |
| TSConfig paths | Paths not matching package.json imports |
When to Use
- After manual editing of package.json, tsconfig.json
- Before committing changes
- When something "feels wrong" after out-of-band edits
- CI verification (all checks should pass)
Notes
- Each audit exits non-zero if issues found
- Prefer running audits over blindly syncing - understand what changed
- If audit finds issues, the corresponding sync skill will fix them