Plugin release checker
Skill joaquimscosta/arkhe-claude-plugins/.claude/skills/plugin-release-checker
Validate plugin content quality before release. Run skill-validator across plugins, verify marketplace.json completeness, check plugin.json version consistency, and detect broken documentation cross-references. Use when preparing a release, before running release.sh, or when user mentions "release check", "pre-release", "plugin-release-checker", or "release validation".From its SKILL.md
npx -y skills add joaquimscosta/arkhe-claude-plugins --skill plugin-release-checkerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 2 commands, including `scripts/check_release_readiness.py --all` and 1 more.
SKILL.md
2.3 KB, 445 tokens by cl100k_base, as published. Nobody here has run it
Plugin Release Checker
Pre-release content quality gate that complements scripts/release.sh. Run before generating the changelog or triggering the release workflow.
Quick Start
Run the validation script to check all plugins:
scripts/check_release_readiness.py --all
Check a specific plugin:
scripts/check_release_readiness.py --plugin core
Release Workflow Integration
/plugin-release-checker ← THIS: validates plugin content quality
↓ (all checks pass)
/changelog ← generates CHANGELOG entry
↓
./scripts/release.sh X.Y.Z ← handles git tag + GitHub Release
Checks Performed
| Check | Description |
|---|---|
| Skill Validation | Run skill-validator across all skills in each plugin |
| Marketplace Sync | Verify all plugins in plugins/ have entries in marketplace.json |
| Version Consistency | Check plugin.json versions match CHANGELOG entries |
| Cross-References | Detect broken links in SKILL.md → WORKFLOW.md, EXAMPLES.md, etc. |
| Required Files | Ensure each plugin has plugin.json and README.md |
| Frontmatter | Validate YAML frontmatter in agents, commands, and skills |
Output
=== Plugin Release Readiness Report ===
Plugin: core (v2.0.0)
✓ All skills pass validation
✓ Marketplace entry found
✓ Version consistent with CHANGELOG
✓ No broken cross-references
Plugin: git (v1.0.0)
✗ Skill 'creating-commit': 1 error (SS002: SKILL.md exceeds 500 lines)
✓ Marketplace entry found
✓ Version consistent with CHANGELOG
✓ No broken cross-references
Summary: 9/10 plugins ready, 1 plugin has issues
Command Options
--all # Check all plugins (default)
--plugin NAME # Check specific plugin
--skip-skill-validator # Skip skill-validator (faster, less thorough)
--format {text,json} # Output format
What ships with it: 4 files
43.0 KB alongside SKILL.md, 4 of them executable
scripts/
- check_release_readiness.pyruns20.6 KB
- validate_cross_references.pyruns11.0 KB
- validate_reference_staleness.pyruns3.5 KB
- validation_utils.pyruns7.8 KB
Gives 0 of the 12 instructions most quality gates skills give in 445 tokens
Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06
- Read full output and check exit codein 45 of 1524, across 40 files
- Verify output confirms the claimin 44 of 1524, across 39 files
- Identify the command that proves the claimin 43 of 1524, across 39 files
- Execute the full verification commandin 36 of 1524, across 30 files
- Produce a verification reportin 34 of 1524, across 18 files
- Review git diff changesin 30 of 1524, across 16 files
- Fix build failures immediatelyin 29 of 1524, across 9 files
- Group findings by severityin 28 of 1524
- State claim only with evidencein 27 of 1524, across 22 files
- Verify regression tests with red-green cyclein 26 of 1524, across 22 files
- Run the full test suitein 26 of 1524, across 25 files
- Run test suite with coveragein 25 of 1524, across 10 files
Said here and by no other author read
- Run the release readiness script before generating changelogs
- Check plugin version consistency against changelogs
- Detect broken documentation cross-references
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.