cladding-init
Use only when the user explicitly names Cladding and asks to initialize, adopt, or refresh it; never use for an ordinary project…
@qwerfunchInstall SkillDevelopment
Skill
/checkpoint
Record a feature checkpoint event pinning the current git HEAD plus a spec digest, so a later rollback can restore the exact pre-change state. Use before a non-trivial feature implementation, before a refactor that touches many files, or whenever the user wants a known-good
Claude Code
$ npx -y skills add purpleeddy/cladding --skill checkpoint --agent claude-code
Codex
$ npx skills add purpleeddy/cladding --skill checkpoint -a codex -y
Cursor
$ npx skills add purpleeddy/cladding --skill checkpoint -a cursor -y
Gemini CLI
$ npx skills add purpleeddy/cladding --skill checkpoint -a gemini-cli -y
GitHub Copilot
$ npx skills add purpleeddy/cladding --skill checkpoint -a github-copilot -y
OpenCode
$ npx skills add purpleeddy/cladding --skill checkpoint -a opencode -y
Windsurf
$ npx skills add purpleeddy/cladding --skill checkpoint -a windsurf -y
SKILL.md
checkpoint.SKILL.mddescription: Record a feature checkpoint event pinning the current git HEAD plus a spec digest, so a later rollback can restore the exact pre-change state. Use before a non-trivial feature implementation, before a refactor that touches many files, or whenever the user wants a known-good safety net the autonomous drive loop can fall back to. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.
Cladding checkpoint
Run `clad checkpoint <featureId>` from the project root. Iron Law backbone Phase 1 (iron-law.md §2.5) — the verb only **stamps** the audit-log entry; it never mutates the working tree or invokes `git commit`. The maintainer keeps the option to freeze the state with a normal git commit on top.
The checkpoint event payload carries:
- `featureId` — the spec id, accepts both `F-NNN` legacy and six-or-more-hex hash shapes; newly authored records emit `F-<hash8>`.
- `gitHead` — full 40-char commit sha at the time of the call (or `null` when the project is not a git repository).
- `specDigest` — sha-256 over the merged spec for replay verification.
- `timestamp` — ISO 8601.
clad checkpoint F-001
clad checkpoint F-a3f9c2e1
The output is a single Pulse line: `✓ checkpoint · <featureId> head=<sha12> digest=<digest12>`. The event lands in `.cladding/events.log.jsonl` as `type: "feature_checkpoint"` and can be inspected with `clad doctor --json` or `clad_get_events` over MCP.
When to use
- Before starting a feature with your AI host so a failed attempt has a known-good target to roll back to.
- Before a manual refactor large enough that `git stash` is unwieldy.
- Right after `clad sync` reports the spec is valid, so the checkpoint pins exactly the validated spec digest the implementation will start from.
Pair with
`clad rollback <featureId>` — prints the maintainer-runnable `git checkout <sha>` for the latest checkpoint and stamps a `feature_rolled_back` event. The pair forms the v0.3.X Iron Law backbone for safe autonomous progress; see `skills/rollback/SKILL.md`.
Read more
description: Record a feature checkpoint event pinning the current git HEAD plus a spec digest, so a later rollback can restore the exact pre-change state. Use before a non-trivial feature implementation, before a refactor that touches many files, or whenever the user wants a known-good safety net the autonomous drive loop can fall back to. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.
Cladding checkpoint
Run `clad checkpoint <featureId>` from the project root. Iron Law backbone Phase 1 (iron-law.md §2.5) — the verb only **stamps** the audit-log entry; it never mutates the working tree or invokes `git commit`. The maintainer keeps the option to freeze the state with a normal git commit on top.
The checkpoint event payload carries:
- `featureId` — the spec id, accepts both `F-NNN` legacy and six-or-more-hex hash shapes; newly authored records emit `F-<hash8>`.
- `gitHead` — full 40-char commit sha at the time of the call (or `null` when the project is not a git repository).
- `specDigest` — sha-256 over the merged spec for replay verification.
- `timestamp` — ISO 8601.
clad checkpoint F-001 clad checkpoint F-a3f9c2e1
The output is a single Pulse line: `✓ checkpoint · <featureId> head=<sha12> digest=<digest12>`. The event lands in `.cladding/events.log.jsonl` as `type: "feature_checkpoint"` and can be inspected with `clad doctor --json` or `clad_get_events` over MCP.
When to use
- Before starting a feature with your AI host so a failed attempt has a known-good target to roll back to.
- Before a manual refactor large enough that `git stash` is unwieldy.
- Right after `clad sync` reports the spec is valid, so the checkpoint pins exactly the validated spec digest the implementation will start from.
Pair with
`clad rollback <featureId>` — prints the maintainer-runnable `git checkout <sha>` for the latest checkpoint and stamps a `feature_rolled_back` event. The pair forms the v0.3.X Iron Law backbone for safe autonomous progress; see `skills/rollback/SKILL.md`.
Stats
16
Stars
4
Forks
Maintained
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
Ships withcladding
For an organization to trust AI with its code, three things must hold — trust, traceability, and stability at scale. cladding wraps your AI coding agent: your intent goes in before it writes, and the result is verified against your spec after, so those three are earned, not assumed. First L4 implementation of the Ironclad standard.
1619 skills6 agents1 MCP
Stars on GitHub
Momentum
- stars in total
- 16
Other skills on cladding.
@qwerfunchInstall Skillblind-author
Impl-blind test/oracle author — writes conformance tests from a spec-only brief. Tool-restricted by definition (no…
@qwerfunchInstall Skillchangelog
Render release notes / a changelog from the cladding spec. Use when the user asks for release notes, a changelog, 릴리즈 노트, 변경 이력,…
@qwerfunchInstall Skillcheck
Run every Iron Law stage and the drift detector suite. Use when the user wants the full project health snapshot, a CI gate, or to…
@qwerfunchInstall Skillclarify
Advance Cladding onboarding after the user answers a pending product question. Use the MCP prepare/apply flow, preserve the…
@qwerfunchInstall Skilldeveloper
Implementer — writes production code, tests, and migrations. The "generic engineer" fallback when no narrower specialist exists.…
@qwerfunchInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about checkpoint.
- Which coding agents can use checkpoint?
- checkpoint installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.