القائمة
Read-only drift check across root SPEC.md, the active change's delta, and the code. Use when the user runs `/co:check` or asks whether the spec and code are in sync. Writes nothing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Coordinate repository work through Colony MCP. Use when an agent starts, resumes, chooses work, claims files, hands off work, records working state, or finishes a task in a repo where Colony tools are available.
Bucket Claude Code and Codex session tokens into Colony tasks and surface improvement suggestions. Use when the user runs `/co:tokens`, asks how many tokens a task spent, why a session got expensive, or what to change next time.
This skill should be used when building data processing pipelines with CocoIndex, a Python library for incremental data transformation. Use when the task involves processing files/data into databases, creating vector embeddings, building knowledge graphs, ETL workflows, or any data pipeline requiring automatic change detection and incremental updates. CocoIndex is Python-native (supports any Python types), has no DSL, and uses version 1.0.0 or later.
Validate, three-way-merge, and archive a colonykit change. Use when the user runs `/co:archive <slug>` or says the change is done. Atomic — either the archive and root-write both land, or neither does.
Execute the next §T task on the current colonykit change. Use when the user runs `/co:build` or asks you to proceed with the next task. Pulls cite-scoped context, executes, on test failure records via backprop gating.
Open a new colonykit spec change. Use when the user runs `/co:change <slug>` or asks to start a new proposal, delta, or change-in-flight. Creates openspec/changes/<slug>/CHANGE.md and opens a task-thread on spec/<slug>.
| name | co-check |
| description | Read-only drift check across root SPEC.md, the active change's delta, and the code. Use when the user runs `/co:check` or asks whether the spec and code are in sync. Writes nothing. |
Read-only drift detection.
spec_read — get rootHash and section shapes.attention_inbox with the user's session id — surface pending handoffs, stalled lanes, and any recent claims by other sessions on SPEC.md#V.* or CHANGE.md#*.x (done), check that the cited files exist and the cited commands still succeed (run them with --dry-run where available).~ (wip), list the session_id that claimed them via task_list + task_timeline.--cross-changes):
task_list filtered on branch prefix spec/.A single report, no writes. Format:
SPEC.md rootHash=abc12345
§V 12 invariants (3 always-on)
§T 18 tasks (11 done, 4 wip, 3 todo)
§B 2 bugs
Active change: add-dark-mode (task #42)
base_root_hash: abc12345 (in sync with root)
deltas: 5 rows (3 add, 2 modify)
Attention:
- codex@x7 claimed packages/spec/src/sync.ts 4m ago
- 1 pending handoff to you from claude@a1
Cross-change (--cross-changes):
none
§V9 of the root spec makes this a hard rule. Never modify SPEC.md or any CHANGE.md from inside /co:check — even to fix a typo. If the user asks for fixes during a check, tell them to run /co:spec or edit the change.