claude-plugins CLAUDE.md

claude-plugins

Language

This is an English-language OSS project. All content — code, documentation, commit messages, PR descriptions, and plugin skill definitions — must be written in English. When porting content from non-English sources, translate it as part of the extraction process.

Plugin Change Checklist

When modifying a plugin's behavior, update ALL of the following in the same commit:

• {plugin}/scripts/*.sh or other code files
• {plugin}/.claude-plugin/plugin.json (bump version, update description)
• .claude-plugin/marketplace.json (mirror version and description)
• README.md: plugin table row, overview, "How it works", "Configuration", and any other references
• Grep the repo for hardcoded values related to the change (branch names, defaults, etc.) and update every occurrence
• After updating, grep the repo for every string the prior version exposed that the new version drops or renames (old version numbers, removed field names, deprecated wording, retired terminology) and confirm zero stale occurrences remain before declaring the commit done. A mechanical stale-string sweep is part of the gate, not an optional check.

Hook Script Conventions

When writing a Claude Code hook script ({plugin}/scripts/*.sh referenced from hooks.json):

• Confirm the hook input schema (cwd, tool_name, tool_input.*, session_id, hook-event-specific fields) before designing the script.
• Read stdin once into a variable, then run multiple jq queries via printf '%s' "$input" | jq .... Never let jq consume stdin directly when more than one field may be needed now or later.
• Resolve repo state with git -C "$cwd" using the cwd field from hook input, not the script's inherited cwd.
• Implement matching logic inside the script (branch on tool_name, inspect tool_input.command, etc.). Conditional fields like if: on hook entries are not honored by Claude Code.

Plugin Testing

"Tests pass" is a strict statement. It means the production path was executed, not that syntax checks succeeded.