Plugin Change Checklist

Use this skill when a change affects plugin behavior, distribution, or the user-facing install experience.

Goals

• Keep the plugin shippable through GitHub marketplace
• Keep README short and installation-first
• Make sure Claude Code can detect the update
• Catch hook regressions before push

Checklist

1. If behavior changed in a way users need to receive, bump both versions:

   • .claude-plugin/plugin.json
   • .claude-plugin/marketplace.json

2. Keep README focused:

   • Prefer one primary example
   • Prefer direct CLI commands over extra prose
   • Avoid repeating behavior that is already explained elsewhere
   • Do not reintroduce curl-based install instructions

3. This plugin uses SessionStart + additionalContext only:

   • No external LLM calls, no API keys
   • All explanations are generated by Claude itself
   • Do not introduce external dependencies

4. Validate the plugin:

   claude plugins validate .
   bash hooks-handlers/session-start.sh | python3 -c "import sys,json; json.load(sys.stdin)"
   

5. Test hook output:

   bash test.sh
   

6. When users say updates are not visible locally, check in this order:

   • claude plugins marketplace update flyai
   • claude plugins update cc-buddy@flyai
   • Reopen Claude Code window
   • If still stale, confirm the manifest version actually changed

Output expectation

When finishing a change, report:

• whether versions were bumped
• what README text changed
• what validation commands passed
• what users should run locally if they need to refresh the plugin