plugin-review

Featured

Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.

Code & Development 323 stars 29 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
84
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Plugin Review Tiered quality review of plugins with dependency-aware scoping. ## When NOT To Use - Reviewing one skill rather than a plugin (use `abstract:skills-eval`) - Reviewing hooks (use `abstract:hooks-eval`) - Tracing `Skill()` references across plugins (use `abstract:skill-graph-audit`) ## Table of Contents - [Tiers](#tiers) - [Orchestration](#orchestration) - [Scope Detection](#scope-detection) - [Module Loading](#module-loading) - [Verdict](#verdict) - [Output Format](#output-format) - [Quality Gate Mode](#quality-gate-mode) - [Configuration](#configuration) ## Tiers | Tier | Trigger | Scope | Depth | Duration | |------|---------|-------|-------|----------| | branch | Default | Affected and related | Quick gates | ~2 min | | pr | Before merge | Affected and related | Standard | ~5 min | | release | Before version bump | All 17 plugins | Full | ~15 min | ## Orchestration 1. **Detect scope**: parse `--tier` flag, find affected plugins from git diff, resolve related plugins from `docs/plugin-dependencies.json` 2. **Plan**: build check matrix (tier x plugin x role) 3. **Execute**: run checks per tier definition 4. **Report**: per-plugin table, aggregate verdict ## Scope Detection Affected plugins: `git diff main --name-only` filtered to `plugins/*/`. Related plugins: load `docs/plugin-dependencies.json`, look up each affected plugin's reverse index to find dependents. Mark as "related" (lighter checks). If `--tier release` or no git diff available...

Details

Author
athola
Repository
athola/claude-night-market
Created
8 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

code-review

Pragmatic code review & pre-push quality gate. Use when the user says "review code", "check code quality", "any issues with this code", "ready to push", "prepare commit", "submit code", "push to remote", or any variation requesting code inspection before merging or pushing.

3 Updated yesterday
Wubabalala
Code & Development Solid

pre-release-review

Pre-release gate for the monorepo — establishes per-plugin release boundaries (each plugin's last tag → HEAD), audits every changed plugin's CHANGELOG against the actual code diff, then hands off to the native `/code-review high --fix` for the deep correctness pass. Use this whenever the operator is about to ship and says "pre-release review", "review before I release", "review what's shipping", "audit the release", "check the release window", "is this ready to tag", or asks to sanity-check accumulated unreleased work before `/release` or `/fleet-release`. Runs BEFORE the release, never mutates version/tags. Trigger even when phrased loosely, as long as the intent is a last look before shipping.

68 Updated today
gtapps
Code & Development Listed

review-code-quality

Use when finishing self-review of an implementation, before requesting PR review, when inspecting someone else's PR or a PR not checked out locally (PR review mode), when a diff updates a domain model attribute (`plan_code` / `role` / `status` 等), or when the user says "コード品質をレビューして" / "品質レビュー". Analyzes the diff across cohesion and coupling (plus business-impact for domain-attribute changes — Ruby/Rails diffs only, skipped when the diff has no .rb/.rake files) and hands off every 🔴/🟠 finding to /polish-before-commit as needs-judgment without editing files. Readability-level fixes (minor renames, simplification, efficiency) are covered by the built-in /code-review skill, not this plugin.

0 Updated 2 days ago
YasuakiOmokawa