HaipingShi

coderail-diagnose

Build a tight, red-capable feedback loop before diagnosing or fixing a bug. Use for regressions, exceptions, failing behavior, intermittent failures, and performance defects in a repository governed by CodeRail.

coderail-frame

Investigate repository evidence, detect candidate domain boundaries, and choose a quick path or one high-impact novice-safe question before drafting a CodeRail contract. Use internally for new, ambiguous, risky, persistent, or cross-module requests whose task boundary is not yet established.

coderail-grill-contract

Orchestrate repository framing, quick-path bypass, one-question guided convergence, typed Contract Drafts, and Draft Deltas into a confirmed CodeRail G/T/S/V/X/P contract. Use explicitly before implementation when a new request needs task boundaries or user-owned decisions.

coderail-tdd-quality

Implement correctness-sensitive behavior with trustworthy red-green slices under CodeRail. Use for features, bug fixes, parsers, validators, domain logic, public APIs, shared utilities, and risky behavior-preserving refactors.

coderail-two-axis-review

Review the active CodeRail task on two independent axes: repository standards and task-contract intent. Use before closeout, for work-in-progress review, or when implementation may be correct-looking but misaligned with scope or acceptance.

align

Before coding, make sure the request actually serves the project goal, and turn it into a clear task with goal, scope, and a way to verify it.

blueprint

Keep simple architecture/data/flow diagrams up to date when the project gets structurally complex.

ci-gate

Run the project's available checks (tests, lint, build) before stopping, handing off, or committing finished work.

doctor

Health-check the project's CodeRail setup and state; reports what is missing or inconsistent and how to fix it.

execute-batch

Work through the approved tasks continuously, staying inside each task's file scope and stop conditions.

handoff

Write a short snapshot so the next session (or another person/agent) can resume without re-discovering everything.

inspect

Rebuild a clear picture of project state (active task, gaps, next step) before resuming or when things feel confusing.

asset-boundary

Tell apart raw material, working notes, and permanent project files so temporary stuff never gets treated as the real thing.

drift-check

Detect when the work has drifted away from the project goal, the task list, or the recorded history.

harness-repair

When the test/check setup itself is broken, fix it without weakening what it verifies.

link

Backfill missing connections in the project history so every change can be traced to a task and a reason.

trace

Record a meaningful action (change, decision, verification) in the project history so it can be found later.