plugin-review

Review Claude Code plugin artifacts for logic bugs, trigger issues, and execution feasibility.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill plugin-review-n0rvyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-review
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/skill-audit/skills/plugin-review
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill plugin-review-n0rvyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide an AI-executor-focused audit of Claude Code plugin artifacts to find logic bugs, trigger failures, and execution feasibility issues that impede reliable runtime behavior and orchestration.

Core Features & Use Cases

  • Detects scope from user input (specific files, entire plugin, recent git changes, or full audit) and lists files for confirmation.
  • Chooses Strategy A (parallel plugin-dev validators + internal reviewer) if plugin-dev is available, or Strategy B (internal reviewer with supporting docs) otherwise, and merges or presents results accordingly.
  • Produces a unified report across nine review dimensions with grouped severities, file:line references, and actionable fixes for Bug-level findings; supports applying fixes on approval.
  • Use Case: Run a focused review after modifying skills or agents to catch dispatch loops, trigger conflicts, and execution edge cases before release.

Quick Start

Ask the plugin-review skill to audit my plugin directory "my-plugin" for logic bugs, trigger issues, and execution feasibility.

Frequently Asked Questions about plugin-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Claude Code plugins for logic bugs and trigger issues?

Audit Claude Code plugins by reviewing manifests, skills, and agents files to identify logic bugs, trigger failures, and execution feasibility issues. Provide specific file paths, entire directories, or recent git diffs to generate grouped findings with file:line references and suggested fixes.

What is the best way to review recent git changes in a Claude Code plugin?

Review recent git changes by passing git diffs to the audit process, which scopes detection to modified files. It analyzes dispatch loops, trigger conflicts, and execution edge cases in those diffs to produce a unified report across nine review dimensions with actionable fixes.

Can I use plugin-dev validators to check manifest and execution feasibility?

Yes, if the plugin-dev environment is available, the audit runs parallel plugin-dev validators alongside an internal reviewer. If unavailable, it falls back to an internal reviewer with supporting documentation to detect execution feasibility issues.

Does the plugin review process support applying fixes automatically?

Yes, the plugin review process supports applying fixes on approval. It produces a unified report grouping severities across nine dimensions with file:line references and suggested fixes for Bug-level findings that can be applied after user confirmation.

Why do my Claude Code plugin triggers conflict during runtime orchestration?

Trigger conflicts occur when plugin manifests, skills, or agents files contain overlapping dispatch logic or execution edge cases. Auditing these artifacts detects trigger failures and execution feasibility issues that impede reliable runtime behavior and orchestration.

What files are required to perform a full Claude Code plugin audit?

A full plugin audit requires access to plugin manifests, skills files, and agents files. Optionally, plugin-dev tools and git diffs enhance the review by providing parallel validators and scoped change detection across the nine review dimensions.