/checkpoint
Create, verify, or list workflow checkpoints after running verification checks.
> /plugin marketplace add affaan-m/ECC> /plugin install ecc@ecc
Command definition
checkpoint.mddescription: Create, verify, or list workflow checkpoints after running verification checks.
Checkpoint Command
Create or verify a checkpoint in your workflow.
Usage
`/checkpoint [create|verify|list] [name]`
Create Checkpoint
When creating a checkpoint:
1. Run `/verify quick` to ensure current state is clean 2. Create a git stash or commit with checkpoint name 3. Log checkpoint to `.claude/checkpoints.log`:
echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .claude/checkpoints.log
4. Report checkpoint created
Verify Checkpoint
When verifying against a checkpoint:
1. Read checkpoint from log 2. Compare current state to checkpoint:
- Files added since checkpoint
- Files modified since checkpoint
- Test pass rate now vs then
- Coverage now vs then
3. Report:
CHECKPOINT COMPARISON: $NAME
============================
Files changed: X
Tests: +Y passed / -Z failed
Coverage: +X% / -Y%
Build: [PASS/FAIL]
List Checkpoints
Show all checkpoints with:
- Name
- Timestamp
- Git SHA
- Status (current, behind, ahead)
Workflow
Typical checkpoint flow:
[Start] --> /checkpoint create "feature-start"
|
[Implement] --> /checkpoint create "core-done"
|
[Test] --> /checkpoint verify "core-done"
|
[Refactor] --> /checkpoint create "refactor-done"
|
[PR] --> /checkpoint verify "feature-start"
Arguments
$ARGUMENTS:
- `create <name>` - Create named checkpoint
- `verify <name>` - Verify against named checkpoint
- `list` - Show all checkpoints
- `clear` - Remove old checkpoints (keeps last 5)
Read more
description: Create, verify, or list workflow checkpoints after running verification checks.
Checkpoint Command
Create or verify a checkpoint in your workflow.
Usage
`/checkpoint [create|verify|list] [name]`
Create Checkpoint
When creating a checkpoint:
1. Run `/verify quick` to ensure current state is clean 2. Create a git stash or commit with checkpoint name 3. Log checkpoint to `.claude/checkpoints.log`:
echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .claude/checkpoints.log
4. Report checkpoint created
Verify Checkpoint
When verifying against a checkpoint:
1. Read checkpoint from log 2. Compare current state to checkpoint:
- Files added since checkpoint
- Files modified since checkpoint
- Test pass rate now vs then
- Coverage now vs then
3. Report:
CHECKPOINT COMPARISON: $NAME ============================ Files changed: X Tests: +Y passed / -Z failed Coverage: +X% / -Y% Build: [PASS/FAIL]
List Checkpoints
Show all checkpoints with:
- Name
- Timestamp
- Git SHA
- Status (current, behind, ahead)
Workflow
Typical checkpoint flow:
[Start] --> /checkpoint create "feature-start" | [Implement] --> /checkpoint create "core-done" | [Test] --> /checkpoint verify "core-done" | [Refactor] --> /checkpoint create "refactor-done" | [PR] --> /checkpoint verify "feature-start"
Arguments
$ARGUMENTS:
- `create <name>` - Create named checkpoint
- `verify <name>` - Verify against named checkpoint
- `list` - Show all checkpoints
- `clear` - Remove old checkpoints (keeps last 5)
Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills
Other commands on ecc.
More commands from other plugins.
build
CommandImplement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.

