// Clear CCB managed agent conversation context with `ccb clear`. Use when the user writes `$ccb-clear`, `$ccb_clear`, or asks to clear/reset one or more CCB agent contexts without restarting or deleting project state.
| name | ccb-clear |
| description | Clear CCB managed agent conversation context with `ccb clear`. Use when the user writes `$ccb-clear`, `$ccb_clear`, or asks to clear/reset one or more CCB agent contexts without restarting or deleting project state. |
| metadata | {"short-description":"Clear CCB agent context"} |
Use this skill to clear provider conversation context for mounted CCB agents.
Commands:
command ccb clear
command ccb clear "$AGENT"
command ccb clear agent1 agent2
Rules:
ccb clear targets all configured mounted agents.ccb clear <agent...> targets only the named agents./clear to each target pane..ccb state, workspaces, auth, sessions, logs, or memory files.ccb kill, ccb -n, or restart commands unless the user explicitly asks for process/runtime reset.Design, edit, or migrate CCB project teams by updating .ccb/ccb.config. Use when the user wants to add, rename, remove, or reorganize CCB agents; choose providers, worktree isolation, models, API shortcuts, single-window or multi-window layout; migrate an old ccb.config to the current windows topology; handle optional skill inheritance or injection requests for agents; or turn a natural-language team/workflow description into a valid CCB config. Only update shared or per-agent memory when the user explicitly asks for workflow memory design.
Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan, design-doc folder, roadmap tree, active implementation-status file, repo cleanup/filesystem plan, ADR/decision log, ideas inbox, or linked planning knowledge base; reconcile Done/In Progress/Next state; resume work from TODO/handoff state; move resolved questions into decisions; promote ideas into formal plan artifacts; or keep plan documents and file-structure planning internally consistent without making this project-specific.
Send a request to a CCB agent with `ask`.
Send a request to a CCB agent with `ask`.
Send a request to a CCB agent with `ask`.
Maintain this CCB project's GitHub-facing release surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README_zh.md, CHANGELOG.md, VERSION, GitHub release notes/assets, repository description/topics, or GitHub Actions release/test status.