Kawaz Claude Plugins
kawaz-claude-plugins is a Claude Code plugin for the Build phase that ships a six-plugin toolkit for debugging, memory, hooks, and session operations across the solo-builder journey.
by kawaz · github.com/kawaz/claude-plugins
Add Kawaz’s six-plugin utility pack for session memory, debugging aids, hooks, plans, and daily agent operations in one Claude Code install.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install kawaz-claude-plugins@kawaz/claude-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:kawaz/claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:kawaz/claude-plugins").
What it does
kawaz-claude-plugins is a community Claude Code plugin collection—six separate extensions in one repo—aimed at builders who want richer session tooling without assembling everything from scratch. Metadata and keywords point at debugging and debugger flows, hook automation, long-horizon memory and JSONL-style storage, command surfaces for plans and daily operations, expertise and external-call guardrails, and idea or reflection capture during early discovery. That spread justifies a journey-wide tag: you might enable only the debugger during Ship, only memory during multi-day Build, or hooks during Operate-style monitoring, but the bundle’s purpose is to improve how Claude Code behaves as an agent environment. It is intermediate complexity because you choose which of the six plugins to enable and how they interact with Bun, npm/npx, pip/venv, or jj-managed workflows mentioned in keywords. Read each plugin’s README inside the repo for exact triggers; this catalog entry describes the bundle shape, not undocumented star counts or install popularity.
Highlights
- Six-plugin collection spanning debugging, memory, hooks, session, plans, and daily operations
- Keywords cover AI-assisted analysis, diffs, JSONL storage, external calls, and misuse prevention patterns
- Includes workflow helpers for ideas, reflections, timelines, and project-scoped agent work
- Bundled marketplace for Claude Code rather than one monolithic skill—pick plugins per task
Why builders use it
Stock Claude Code sessions lose context, lack structured debug workflows, and force you to cobble together hooks, memory, and planning utilities one at a time.
After installing the collection, you enable targeted Kawaz plugins so sessions gain memory, debugging, hooks, and planning commands matched to how you actually ship.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is kawaz-claude-plugins for?
Claude Code users who run long, tool-heavy sessions and want Kawaz’s debugging, memory, hook, and planning plugins bundled in one marketplace install.
When should I use kawaz-claude-plugins?
Use it when you are extending Claude Code itself—session persistence, structured debugging, hooks, or daily agent operations—not when you only need one app integration.
How do I add kawaz-claude-plugins to my agent?
Add the kawaz/claude-plugins repository to Claude Code, enable the subset of the six plugins you need, and follow per-plugin README steps for Bun, npm, pip, or jj tooling where required.
Comments
Share how you use kawaz-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.