cliff-code

My personal Claude Code plugin marketplace. Various hobby plugins, some serious, some very unserious.

Install the marketplace

/plugin marketplace add cliffmeyers/cliff-code

Then install individual plugins:

/plugin install <plugin-name>@cliff-code

Plugins

Name	What it does
commit-message	Authors commit messages matching repo conventions. Never commits.

A word on what's in here

These are personal experiments. They're packaged properly (manifest, docs, CI) but may or may not be useful to others.

Plugins that execute shell commands are clearly noted in their own README — read those before installing, and feel free to inspect the scripts in this repo.

Adding a new plugin

For my own future reference (and any contributor's):

1. Create plugins/<plugin-name>/ and plugins/<plugin-name>/.claude-plugin/.
2. Write plugins/<plugin-name>/.claude-plugin/plugin.json with name, description, author, homepage, repository, license, keywords. Leave version out — see CLAUDE.md for why.
3. Add the component dirs you need at the plugin root: hooks/, skills/, commands/, agents/, etc.
4. Write plugins/<plugin-name>/README.md (install command, usage, security notes, any disclaimers).
5. Add an entry to .claude-plugin/marketplace.json under plugins with name, source: ./plugins/<plugin-name>, description, plus homepage / repository / license / keywords.
6. Validate: claude plugin validate .
7. Test in dev: claude --plugin-dir ./plugins/<plugin-name>
8. Test the full install path: /plugin marketplace add /path/to/cliff-code then /plugin install <plugin-name>@cliff-code in a fresh session.
9. Open a PR — main takes squash merges only, gated on CI. Merging is the release — plugins here carry no version field, so Claude Code versions them by commit SHA and users pick up changes on the next /plugin update.

See CLAUDE.md for more detail on the dev workflow, granularity principles, and how versioning works here.

License

MIT. Use, fork, modify freely.

Issues / feedback

File an issue on the GitHub repo.

For anything security-related, don't open a public issue — see SECURITY.md for the private disclosure path and what's in scope.