co-check

Validate synchronization between spec, code, and active change deltas in a Colony environment.

3|Updated Apr 23, 2026

Search Tags:#code review #drift detection #conflict resolution #spec synchronization #software validation

Ready to run

npx skills add https://github.com/opencue/colony --skill co-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: co-check
Source: https://github.com/opencue/colony/tree/main/skills/check
Command: npx skills add https://github.com/opencue/colony --skill co-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for verifying that the root SPEC.md, the active change's delta, and the code are in sync, preventing errors and inconsistencies.

Core Features & Use Cases

Drift Detection: Identifies discrepancies between the spec and code.
Attention Inbox: Provides updates on pending handoffs and stalled lanes.
Conflict Surface: Detects cross-change conflicts between spec lanes.
Read-only Operation: Ensures that no modifications are made to the spec or code within the Skill.

Quick Start

Run the /co:check command to check for any drift between your spec and code.

Frequently Asked Questions about co-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect spec and code drift in a Colony environment?▼

Drift detection validates synchronization between your root spec, active change deltas, and code. It identifies discrepancies, lists pending handoffs, and surfaces stalled lanes without modifying any files.

What is the best way to identify cross-change conflicts between spec lanes?▼

Cross-change conflict detection validates synchronization between active change deltas and the root spec. This read-only operation surfaces inconsistencies between overlapping spec lanes without modifying code.

Can I use this to check pending handoffs and stalled lanes without modifying code?▼

Yes, you can check pending handoffs and stalled lanes without modifying code. The validation operates in read-only mode, ensuring no changes are made to the spec or code while surfacing inconsistencies.

How do I validate software validation and spec synchronization step by step?▼

Run the synchronization check command to validate software and spec alignment. This scans active change deltas against the root spec and code, listing any drift, pending handoffs, or cross-change conflicts.

Does this code review tool automatically fix drift between spec and code?▼

No, this code review tool does not automatically fix drift. It operates strictly in read-only mode to identify discrepancies and conflicts, ensuring no modifications are made to your spec or code.

Why does co-check report stalled lanes during conflict resolution?▼

Stalled lanes are reported because the tool validates active change deltas against the root spec to detect synchronization issues. Identifying these stalled lanes is part of the read-only drift detection and conflict surfacing process.