Back to Workflow & Productivity

skill-review

skill auditAI agent qualitycode reviewdependency managementskill validationdeveloper toolsworkflow automationAI assistant maintenance
⭐ 860πŸ“„ MITπŸ•’ 2026-06-11Source β†—

Install this skill

npx skills add jezweb/claude-skills

Works across Claude Code, Cursor, Codex, Copilot & Antigravity

The skill-review tool maintains high-quality standards for AI-agent skill sets by performing automated and manual integrity checks. It addresses the common issue of 'skill rot'β€”where AI agents provide outdated code, non-existent API imports, or stale library patternsβ€”by executing a rigorous nine-phase audit. The process evaluates codebase consistency against official documentation, validates YAML frontmatter, and ensures dependencies remain current. By automating syntactical checks and providing a structured framework for manual verification, the tool prevents hallucinations caused by obsolete development practices. It classifies issues by severity, distinguishing between critical API mismatches and minor formatting errors. Whether upgrading a skill version or preparing a new submission, this process ensures that bundled resources, README files, and code examples remain accurate, functional, and aligned with current production standards.

When to Use This Skill

  • β€’Auditing an AI skill prior to submission to a public repository
  • β€’Fixing hallucinated API patterns in legacy skill codebases
  • β€’Updating dependencies that have exceeded a 90-day staleness threshold
  • β€’Synchronizing multiple documentation files like README and SKILL.md
  • β€’Refactoring codebases when a library moves to a new major version

How to Invoke This Skill

Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:

  • β€œCheck this skill for outdated API patterns
  • β€œRun the 9-phase audit on the current skill
  • β€œReview this directory for breaking changes
  • β€œScan the skill for stale dependencies and fix them
  • β€œValidate the schema and imports for this project

Pro Tips

  • πŸ’‘Integrate the automated review scripts (e.g., `./scripts/review-skill`) into your CI/CD pipeline to continuously monitor skill health and catch issues early.
  • πŸ’‘Prioritize fixes based on the 'Severity' categorization (Critical, High, Medium, Low), focusing first on security vulnerabilities and breaking changes that impact core functionality.
  • πŸ’‘Leverage the 'Auto-fix unambiguous' feature for efficient resolution of minor issues, but always perform a human review for architectural or design-related changes.

What this skill does

  • β€’Execute automated 9-phase audits for code and configuration accuracy
  • β€’Identify and resolve non-existent API imports and method signature drift
  • β€’Validate YAML frontmatter and directory structure for discovery optimization
  • β€’Generate standardized audit reports with severity-based classification
  • β€’Perform version control management including semantic versioning bumps

When not to use it

  • βœ•Running on non-technical documents that lack API or schema definitions
  • βœ•Performing initial conceptual brainstorming where structure is not yet defined

Example workflow

  1. Invoke /review-skill <skill-name> to initiate the process
  2. Allow the automated script to validate YAML and link integrity
  3. Review the audit report to identify critical API mismatches
  4. Apply auto-fixes for unambiguous issues like missing imports
  5. Manually verify architectural choices for high-severity findings
  6. Commit the updated files with a generated changelog

Prerequisites

  • –Active AI-agent development environment
  • –Access to the target skill repository
  • –Installed review-skill bash scripts

Pitfalls & limitations

  • !Auto-fixes may not resolve complex architectural inconsistencies
  • !Requires manual intervention for breaking changes that impact logic
  • !False positives can occur if local documentation is not up to date

FAQ

How does it decide between auto-fixing and asking the user?
It auto-fixes unambiguous errors like broken imports where clear evidence exists, but it halts to ask the user if the change involves architectural decisions or breaking API updates.
Can it update my version numbers automatically?
Yes, it evaluates changes and suggests appropriate semantic versioning bumps based on whether the fix is a patch, minor feature, or major API change.
What happens if a dependency is found to be stale?
If a dependency is older than 90 days, the audit flags it as a medium-severity issue, prompting you to verify compatibility and update the version.

How it compares

Unlike a generic code review prompt, this tool utilizes a rigid 9-phase protocol specifically calibrated for AI agent metadata, bundled resource integrity, and external documentation syncing.

Source & trust

⭐ 860 starsπŸ“„ MITπŸ•’ Updated 2026-06-11
πŸ“„ Full skill instructions β€” original source: jezweb/claude-skills
# Skill Review Skill

## Process

Invoke: /review-skill <skill-name> or use this skill when detecting outdated patterns

**Production evidence**: better-auth audit (2025-11-08) - found 6 critical issues including non-existent API imports, removed 665 lines incorrect code, implemented v2.0.0

---

## 9-Phase Audit

1. **Pre-Review**: Install skill, check version/date, test discovery
2. **Standards**: Validate YAML, keywords, third-person style, directory structure
3. **Official Docs**: WebFetch/Context7 verify API patterns, GitHub updates, npm versions, production repos
4. **Code Examples**: Verify imports exist, API signatures match, schema consistency, templates work
5. **Cross-File Consistency**: Compare SKILL.md vs README.md, bundled resources match files
6. **Dependencies**: Run ./scripts/check-versions.sh, check breaking changes, verify "Last Verified"
7. **Categorize**: Severity (πŸ”΄ Critical / 🟑 High / 🟠 Medium / 🟒 Low) with evidence (GitHub/docs/npm)
8. **Fix**: Auto-fix unambiguous, ask user for architectural, update all files, bump version
9. **Verify**: Test discovery, templates work, no contradictions, commit with changelog

**Automated** (via ./scripts/review-skill.sh): YAML syntax, package versions, broken links, TODOs, file org, staleness

**Manual** (AI): API methods vs docs, GitHub issues, production comparisons, code correctness, schema consistency

---

## Severity Classification

πŸ”΄ **CRITICAL**: Non-existent API/imports, invalid config, missing dependencies

🟑 **HIGH**: Contradictory examples, inconsistent patterns, outdated major versions

🟠 **MEDIUM**: Stale minors (>90d), missing docs sections, incomplete errors

🟒 **LOW**: Typos, formatting, missing optional metadata

## Fix Decision

**Auto-fix**: Unambiguous (correct import from docs), clear evidence, no architectural impact

**Ask user**: Multiple valid approaches, breaking changes, architectural choices

## Version Bumps

- **Major** (v1β†’v2): API patterns change
- **Minor** (v1.0β†’v1.1): New features, backward compatible
- **Patch** (v1.0.0β†’v1.0.1): Bug fixes only

---

## Example: better-auth Audit (2025-11-08)

**πŸ”΄ CRITICAL #1**: Non-existent d1Adapter import from 'better-auth/adapters/d1'
- **Evidence**: Official docs show drizzleAdapter, GitHub has no d1Adapter export, 4 production repos use Drizzle/Kysely
- **Fix**: Replaced with drizzleAdapter from 'better-auth/adapters/drizzle'

**Result**: 3 files deleted (obsolete), 3 created (correct patterns), +1,266 lines, v1.0β†’v2.0, 3.5 hours

---

## Issues Prevented (10)

1. **Fake API adapters** - Non-existent imports
2. **Stale API methods** - Changed signatures
3. **Schema inconsistency** - Different table names
4. **Outdated scripts** - Deprecated approaches
5. **Version drift** - Packages >90 days old
6. **Contradictory examples** - Multiple conflicting patterns
7. **Broken links** - 404 URLs
8. **YAML errors** - Invalid frontmatter
9. **Missing keywords** - Poor discoverability
10. **Incomplete bundled resources** - Listed files don't exist

---

## Bundled Resources

**Planning**: ~/.claude/skills/../planning/SKILL_REVIEW_PROCESS.md or repo planning/SKILL_REVIEW_PROCESS.md (complete 9-phase guide)

**Scripts**: Repo root scripts/review-skill.sh (automated validation)

**Commands**: Repo root commands/review-skill.md (slash command, symlinked to ~/.claude/commands/)

**References**: references/audit-report-template.md (output template)

---

**Last Verified**: 2026-01-09 | **Version**: 1.0.1

How to Use This Skill Unit

Option A: Project-Specific (Recommended)

  1. Click "Download" above
  2. In your project, create the directory: .agent/skills/skill-review/
  3. Save the file as SKILL.md
  4. The agent will automatically discover the skill based on its description.

Option B: Global Installation (All Agents)

Save the file to these locations to make it available across all projects:

  • Claude Code: ~/.claude/skills/jezweb/claude-skills/skill-review/SKILL.md
  • Cursor: ~/.cursor/skills/jezweb/claude-skills/skill-review/SKILL.md
  • Antigravity: ~/.gemini/antigravity/skills/jezweb/claude-skills/skill-review/SKILL.md

πŸš€ Install with CLI:
npx skills add jezweb/claude-skills

Read the Master Guide: Mastering Agent Skills β†’

Recommended Rules

View more rules β†’

Recommended Workflows

View more workflows β†’

Recommended MCP Servers

View more MCP servers β†’

Take It Further

Maximize your productivity with these powerful resources

πŸ“‹

Define Your Standards

Set up coding standards to ensure this workflow produces consistent, high-quality results.

Browse Rules Library
πŸ“–

Master Workflows

Learn how to create custom workflows, use Turbo Mode, and build your automation library.

Complete Guide

How to use this Skill in Claude Code & Cursor

For Claude Code (CLI)

To use this skill in Claude Code, copy the rule content into your project's custom instructions or follow our Add-Skill CLI guide. This ensures Claude follows your standards during every code generation.

For Cursor & Windsurf

For Cursor or Windsurf, individual skills are best used in the "Rules for AI" section. This specific unit helps the agent avoid workflow & productivity issues, leading to cleaner, more efficient code.

Why the skill format matters: the standardized Agent Skills format lets your AI agent load detailed instructions only when they are relevant, keeping your prompt clean while improving results.

Source & attribution

This skill is categorized under Workflow & Productivity and is published by JezWeb, maintained in jezweb/claude-skills.

← Browse All Agent Skills
Sponsored AI assistant. Recommendations may be paid.