Menu
Run the full CI verification suite locally (format, lint, test, snapshots). Use before committing or to check if changes pass CI.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when inside a cella dev container and you need to manage branches, dispatch tasks, run parallel agents, or interact with other containers. Also use when you see CELLA_DAEMON_ADDR in the environment or /cella/bin/cella exists.
Use when running a systematic test sweep of the cella worktree/task system from inside a container. Also use after modifying the daemon, agent CLI, or task manager, before releases, or after bug fixes.
Research devcontainer spec, official CLI, and VS Code extension behavior before making design decisions. Use this skill whenever implementing devcontainer commands, options, lifecycle hooks, or features — or when behavior is ambiguous, when fixing spec compliance issues, or when the user asks how something works in the original devcontainer tools. Also use before answering questions about how cella should behave when you're not certain of the correct behavior. Trigger on any devcontainer property name, lifecycle hook, feature resolution, Docker Compose integration, port forwarding, or environment variable handling question.
| name | verify |
| description | Run the full CI verification suite locally (format, lint, test, snapshots). Use before committing or to check if changes pass CI. |
Run all CI checks in sequence, stopping on first failure. Report each step's result clearly.
cargo fmt --all -- --check
cargo clippy --workspace --all-features --all-targets -- -D warnings -D clippy::all
cargo test --workspace
cargo insta test --workspace --check --unreferenced=reject
If any step fails:
cargo fmt --all to fix, then report what changed#[allow(clippy::...)])cargo insta review and assess whether the new snapshots are correct