cct

Plugin cct from marketplace dagonet in dagonet/claude-code-toolkit. Commands read from the repo's manifest — yesterday.

Skills (9)

• challenge

  Challenge a plan, design, or approach in two structured passes — scope/necessity, then correctness/completeness. Use before executing any plan.

• commit

  Stage and commit changes with native git, after showing the user exactly what will be committed. Triggers on /cct:commit.

• contribute-upstream

  Push project improvements back to the claude-code-toolkit template. Triggers on /cct:contribute-upstream.

• jev

  Switch the optional Jev spawn router on or off for this clone, or show its status or report. Triggers on /cct:jev.

• karpathy-guidelines

  Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code.

• mcp-usage

  Occasional MCP procedures — use when digesting a large input, extracting structured data, mapping an unfamiliar repo, looking up a library API, or running a headless batch.

• retro-review

  Review the local subagent-failure retro ledger, user-level config drift, and which consumer repos are behind the toolkit version. Triggers on /cct:retro-review.

• sprint

  Run a sprint backlog as parallel subagent workstreams with rebase-before-merge and gate enforcement. Triggers on /cct:sprint.

• sync-template

  Pull template updates into the current project. Triggers on /cct:sync-template.

Subagents (10)

• Explore

  Read-only codebase search. Returns ranked file:line findings with one-line reasons — never whole files, never edits. Use for "where is X", "how does Y work", "list all uses of Z".

• architect

  Reviews architecture, provides implementation guidance, maintains ADRs and docs. Does NOT write application code.

• code-reviewer

  Reviews code for quality, style, structure, and test coverage. Posts categorized findings. Does NOT write code.

• coder

  Use this agent to implement any kind of software changes in a repository with high-quality engineering standards.

• dotnet-coder

  Use this agent to implement .NET (C#) changes in a repository with high-quality engineering standards. Optimized for task-file driven automation (implement -> build/test -> update task logs -> iterate on review feedback -> commit when approved). <example> Context: A task file describes a feature to

• java-coder

  Use this agent to implement Java (Spring Boot) changes in a repository with high-quality engineering standards. Optimized for task-file driven automation (implement -> build/test -> update task logs -> iterate on review feedback -> commit when approved). <example> Context: A task file describes a fe

• ops

  Environment and tooling executor. Handles setup, downloads/installs, binary/file operations, one-off tool runs, diagnostics, and log collection. Does NOT author application code and does NOT merge.

• python-coder

  Use this agent to implement Python changes in a repository with high-quality engineering standards. Optimized for task-file driven automation (implement -> build/test -> update task logs -> iterate on review feedback -> commit when approved). <example> Context: A task file describes a feature to imp

• rust-coder

  Use this agent to implement Rust/Tauri changes in a repository with high-quality engineering standards. Optimized for task-file driven automation (implement -> build/test -> update task logs -> iterate on review feedback -> commit when approved). <example> Context: A task file describes a feature to

• tester

  Verifies features against acceptance criteria using automated tests, data inspection, and log analysis. Posts findings on GitHub issues.

Hooks (20)

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/cct-session.sh"

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" retro-brief

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" verify-hooks

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" jev-notice

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" now-brief

• PreToolUse

  f="${CLAUDE_PLUGIN_ROOT}/hooks/dispatch.sh"; [ -r "$f" ] || { echo "BLOCKED: cct plugin files are missing (the plugin was upgraded or removed while this session ran) -- restart this session." >&2; exi

• PreToolUse

  f="${CLAUDE_PLUGIN_ROOT}/hooks/dispatch.sh"; [ -r "$f" ] || { echo "BLOCKED: cct plugin files are missing (the plugin was upgraded or removed while this session ran) -- restart this session." >&2; exi

• PreToolUse

  f="${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh"; [ -r "$f" ] || { echo "BLOCKED: cct plugin files are missing (the plugin was upgraded or removed while this session ran) -- restart this session." >&2; exi

• PreToolUse

  f="${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh"; [ -r "$f" ] || { echo "BLOCKED: cct plugin files are missing (the plugin was upgraded or removed while this session ran) -- restart this session." >&2; exi

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" read-size-gate

• PreToolUse

  f="${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh"; [ -r "$f" ] || { echo "BLOCKED: cct plugin files are missing (the plugin was upgraded or removed while this session ran) -- restart this session." >&2; exi

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" model-floor

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" jev-route

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" enforce-delegation

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" agent-budget-warn

• PostToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" bash-output-guard

• PostToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" post-edit-build

• SessionEnd

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/cct-session.sh" end

• SubagentStop

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" enforce-agent-contract

• SubagentStop

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh" retro-ledger