kanso

Plugin kanso from marketplace cyze in blakecyze/skills. Commands read from the repo's manifest — today.

Skills (12)

• kanso-audit

  Use when the user asks for a code review, audit, pre-PR check, quality sweep, or pattern analysis of a diff, branch, module, or codebase. Also use when the user asks to "check" or "look over" their code for issues.

• kanso-commit

  Use when the user asks to commit changes, stage their work, write commit messages, or split the working tree into logical commits.

• kanso-context

  Use when the user asks to update, prune, audit, or create AGENTS.md, CLAUDE.md, or other agent context files. Also use when the user says their AI agents keep making the same mistakes and they want to fix it at the context level.

• kanso-council

  Use when the user wants a stronger, multi-model, or cross-checked audit: \"convene the council\", \"council review\", \"audit with codex/grok/gemini too\", \"second opinion on this diff\", \"multi-engine audit\". Detects other agent CLIs, runs kanso-audit's framework on each in parallel, and merges

• kanso-handoff

  Use when the user wants the current session's context packaged for the next one: \"package this session\", \"carry this context over\", \"before I /clear\", \"handoff\", \"save where we are\", \"compact this into a prompt for next time\". Writes one dense, machine-readable file and prints the resume

• kanso-nuclear

  Use when the user asks for a nuclear review, a thermonuclear audit, a deep maintainability sweep, a structural audit of the whole codebase, or a "harsh" pass on a branch. Stricter and more structural than /kanso-audit.

• kanso-pr

  Use when the user asks to write a pull request description, open a PR, draft PR notes, or summarise a branch for review.

• kanso-principles

  Use when generating, reviewing, modifying, or discussing any code. Sets standing anti-dilution rules for all code-related work. Auto-loads; not directly invoked by the user.

• kanso-prompting

  Use when rewriting, sharpening, or producing a prompt for Claude or another current frontier model. Sets standing rules for getting better LLM output through better prompts. Loaded by /kanso-task; not directly invoked by the user.

• kanso-refactor

  Use when the user asks to clean up, tighten, simplify, de-bloat, de-slop, or refactor code. Also use when acting on findings from /kanso-audit or /kanso-nuclear. Behaviour-preserving only.

• kanso-task

  Use when the user wants a task done well rather than fast, wants a rough or underspecified request sharpened before it runs, or asks for a careful, principled pass at a piece of work.

• kanso-unasked

  Use when the user wants to see or clean up what an agent did beyond the request, such as "what did you add that I didn't ask for", "did you go beyond the brief", "scope creep", "what decisions did you make for me", "undo the extras", or "clean up what I didn't ask for". Not for general code review (

Hooks (1)

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/kanso-verify.sh

Similar plugins