ccb-clear
The ccb-clear skill executes the `ccb clear` command to reset conversation context for Claude Code Bridge agents without removing project state, configuration, or session data. Use this when a user requests to clear or reset CCB agent contexts via commands like `$ccb-clear`, `$ccb_clear`, or explicit reset requests, targeting all mounted agents or specific named agents as needed.
git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge /tmp/ccb-clear && cp -r /tmp/ccb-clear/inherit_skills/codex_skills/ccb-clear ~/.claude/skills/ccb-clearSKILL.md
# CCB Clear Use this skill to clear provider conversation context for mounted CCB agents. In the CCB source checkout, this skill is only for clearing the active work-environment CCB collaboration with the installed release `ccb`. It is not a source validation workflow. For testing current source changes, use `/home/bfly/yunwei/ccb_source/ccb_test` from the dedicated external test project `/home/bfly/yunwei/test_ccb2` instead. Other external test projects require explicit `CCB_TEST_ROOTS` or `CCB_SOURCE_ALLOWED_ROOTS`. Commands: ```bash command ccb clear ``` ```bash command ccb clear "$AGENT" ``` ```bash command ccb clear agent1 agent2 ``` Rules: - `ccb clear` targets all configured mounted agents. - `ccb clear <agent...>` targets only the named agents. - This sends provider-native `/clear` to each target pane. - It does not delete `.ccb` state, workspaces, auth, sessions, logs, or memory files. - Do not use `ccb kill`, `ccb -n`, or restart commands unless the user explicitly asks for process/runtime reset. - After running the command, report the command output. Do not poll or wait.
Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README_zh.md, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state, or GitHub Actions release/test status.
Private built-in CCB configuration skill for agentroles.ccb_self. Design, edit, validate, and prepare reloads for .ccb/ccb.config, role bindings, providers, windows, workspaces, tool windows, sidebar, and provider startup inputs. Use only inside ccb_self; non-self agents should delegate CCB config changes to ccb_self.
Diagnose and repair CCB ask/job/message/reply/artifact/callback lineage. Use for missing replies, incomplete artifacts, pending callbacks, retry/resubmit/ack decisions, reply delivery problems, or work-chain resume advice.
Diagnose CCB runtime, mounted daemon graph, tmux namespace and panes, provider context, queue/inbox/trace, replies/artifacts, config drift, and storage boundaries. Use when the user asks what is broken, which agent is stuck, whether CCB is mounted, why a reply did not arrive, or what to check first.
Recover CCB agents, panes, mounts, provider contexts, API/provider failures, config reload aftermath, clear operations, and guarded single-agent restarts. Use when the user asks to fix, recover, restart if safe, clear context, reload, remount, or keep work going after provider/API failure.
Send a request to a CCB agent with `ask`.
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.