plugin-ops

Plugin plugin-ops in iVintik/claude-plugin-ops. Commands read from the repo's manifest — 1 month ago.

Skills (7)

• diagnose

  Diagnose why a Claude Code plugin skill fails to load, doesn't trigger when expected, errors out, or behaves unexpectedly. Use proactively whenever you notice a plugin or skill misbehaving, or when the user reports something like: \"why isn't this working\", \"plugin not triggering\", \"skill broken

• fix

  Fix open issues tracked in a plugin's ISSUES.md with non-regression safety. Use when the user asks to \"fix plugin issues\", \"resolve plugin bugs\", \"fix this issue\", \"handle this bug\", \"implement the fix\", or mentions fixing tracked plugin problems. Works with ISSUES.md entries created by /p

• issues

  Track bugs and problems in a local ISSUES.md file. Use when the user wants to log, note, or record a problem for later — not fix it now. Also use for: listing what's currently tracked, marking an ISSUE-NNN as resolved, or updating issue status. Key triggers: \"log it\", \"note it somewhere\", \"what

• marketplace

  ALWAYS invoke this skill when the user mentions \"marketplace\" in connection with creating, managing, populating, or querying a plugin marketplace they own. Trigger phrases include: \"init marketplace\", \"create marketplace\", \"add to marketplace\", \"publish to marketplace\", \"list marketplace\

• optimize

  Optimize a Claude Code plugin — reduce knowledge size, improve skill descriptions, remove dead references, condense verbose content. Use when the user asks to \"slim down\", \"clean up\", \"optimize\", \"reduce size\", \"make plugin smaller\", \"trim plugin\", \"reduce footprint\", \"condense\", \"s

• reflect

  Run a comprehensive health audit on a Claude Code plugin — checks structure, skills quality, knowledge size, hooks, MCP config, and cross-references. Use when the user asks to \"analyze plugin health\", \"audit plugin\", \"assess plugin quality\", \"review plugin structure\", \"run self-assessment\"

• release

  Release a Claude Code plugin — bump its version, commit, push, and tag. Use whenever the user wants to release, version-bump, ship, or publish a plugin (any project with a .claude-plugin/ directory). Covers phrases like \"release my plugin\", \"bump plugin version\", \"ship it\", \"publish a new ver

Subagents (3)

• plugin-auditor

  Comprehensive health audit of a Claude Code plugin — checks structure, skills quality, knowledge size, hooks, MCP config, cross-references, and issues. Use when the user asks to analyze plugin health, audit a plugin, assess quality, or run a self-assessment.

• plugin-diagnostician

  Diagnoses root causes when a plugin skill fails to load, doesn't trigger, errors out, or behaves unexpectedly. Use proactively when any plugin issue is detected, or when the user asks to debug/diagnose a plugin.

• plugin-optimizer

  Analyzes a Claude Code plugin for optimization opportunities — knowledge size reduction, skill clarity improvements, dead reference removal. Runs in dry-run mode by default.

Hooks (2)

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/guard-plugin-cache.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/guard-plugin-cache.sh