shancheas
ff6814d038
- Introduced coding standards for TypeScript and React in SKILL.md. - Added continuous learning skill with configuration and evaluation scripts. - Created detail layout guidelines for read-only pages. - Established form layout rules for data-entry forms. - Documented project guidelines for the frontend monorepo. - Implemented security review checklist for frontend/Electron applications. - Developed a verification loop skill for comprehensive session checks. This commit enhances the skill set available for developers, ensuring adherence to best practices and improving code quality.
1.5 KiB
1.5 KiB
Checkpoint Command
Create or verify a checkpoint in your workflow.
Usage
/checkpoint [create|verify|list] [name]
Create Checkpoint
When creating a checkpoint:
- Run
/verify quickto ensure current state is clean - Create a git stash or commit with checkpoint name
- Log checkpoint to
.cursor/checkpoints.log:
echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .cursor/checkpoints.log
- Report checkpoint created
Verify Checkpoint
When verifying against a checkpoint:
-
Read checkpoint from log
-
Compare current state to checkpoint:
- Files added since checkpoint
- Files modified since checkpoint
- Test pass rate now vs then
- Coverage now vs then
-
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 checkpointverify <name>- Verify against named checkpointlist- Show all checkpointsclear- Remove old checkpoints (keeps last 5)