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
/rollback
Record a rollback event and print the maintainer-runnable git command for the most recent checkpoint of a feature. Use when an implementation attempt failed, an autonomous drive loop hit RETRY_THRESHOLD, or the user wants to abandon the current attempt and restore the
Claude Code
$ npx -y skills add purpleeddy/cladding --skill rollback --agent claude-code
Codex
$ npx skills add purpleeddy/cladding --skill rollback -a codex -y
Cursor
$ npx skills add purpleeddy/cladding --skill rollback -a cursor -y
Gemini CLI
$ npx skills add purpleeddy/cladding --skill rollback -a gemini-cli -y
GitHub Copilot
$ npx skills add purpleeddy/cladding --skill rollback -a github-copilot -y
OpenCode
$ npx skills add purpleeddy/cladding --skill rollback -a opencode -y
Windsurf
$ npx skills add purpleeddy/cladding --skill rollback -a windsurf -y
SKILL.md
rollback.SKILL.mddescription: Record a rollback event and print the maintainer-runnable git command for the most recent checkpoint of a feature. Use when an implementation attempt failed, an autonomous drive loop hit RETRY_THRESHOLD, or the user wants to abandon the current attempt and restore the pre-checkpoint state. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.
Cladding rollback
Run `clad rollback <featureId>` from the project root. The verb is the partner of `clad checkpoint` (iron-law.md §2.5 Iron Law backbone Phase 1) — it stamps a `feature_rolled_back` event into `.cladding/events.log.jsonl` and prints the `git checkout <sha>` command the maintainer can run. **Cladding does not run the checkout itself** — the host's branch policy, dirty-working-tree state, or detached-HEAD concerns may demand a non-default strategy, so the decision stays with the maintainer.
- `-r, --reason <reason>` — optional free-text reason recorded on the event payload. Useful for post-mortems and the Librarian's archival flow.
clad rollback F-001
clad rollback F-a3f9c2e1 --reason "specialist dispatched a regression on the L1 lint gate"
The output is a single Pulse line plus the restoration command:
✓ rollback · F-a3f9c2e1 target head=<sha12> ts=<iso>
Run: git checkout <sha40>
When the latest checkpoint has no `gitHead` (the project is not a git repo), the verb prints `No git head pinned — restore spec.yaml manually from VCS history.` instead.
Exit codes
- `0` — rollback event stamped, restoration command printed.
- `1` — no prior checkpoint exists for the feature; nothing to roll back to. Run `clad checkpoint <featureId>` next time before mutating.
- `2` — feature id argument missing.
When to use
- After an attempt that ended with the gate stuck, failing repeatedly, or erroring out.
- After a manual implementation attempt that introduced a regression you don't want to bisect.
- Before retrying the same feature so the next attempt starts from a known-good HEAD instead of an in-progress mess.
Pair with
`clad checkpoint <featureId>` — stamps the safety net rollback restores from. See `skills/checkpoint/SKILL.md`.
Read more
description: Record a rollback event and print the maintainer-runnable git command for the most recent checkpoint of a feature. Use when an implementation attempt failed, an autonomous drive loop hit RETRY_THRESHOLD, or the user wants to abandon the current attempt and restore the pre-checkpoint state. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.
Cladding rollback
Run `clad rollback <featureId>` from the project root. The verb is the partner of `clad checkpoint` (iron-law.md §2.5 Iron Law backbone Phase 1) — it stamps a `feature_rolled_back` event into `.cladding/events.log.jsonl` and prints the `git checkout <sha>` command the maintainer can run. **Cladding does not run the checkout itself** — the host's branch policy, dirty-working-tree state, or detached-HEAD concerns may demand a non-default strategy, so the decision stays with the maintainer.
- `-r, --reason <reason>` — optional free-text reason recorded on the event payload. Useful for post-mortems and the Librarian's archival flow.
clad rollback F-001 clad rollback F-a3f9c2e1 --reason "specialist dispatched a regression on the L1 lint gate"
The output is a single Pulse line plus the restoration command:
✓ rollback · F-a3f9c2e1 target head=<sha12> ts=<iso> Run: git checkout <sha40>
When the latest checkpoint has no `gitHead` (the project is not a git repo), the verb prints `No git head pinned — restore spec.yaml manually from VCS history.` instead.
Exit codes
- `0` — rollback event stamped, restoration command printed.
- `1` — no prior checkpoint exists for the feature; nothing to roll back to. Run `clad checkpoint <featureId>` next time before mutating.
- `2` — feature id argument missing.
When to use
- After an attempt that ended with the gate stuck, failing repeatedly, or erroring out.
- After a manual implementation attempt that introduced a regression you don't want to bisect.
- Before retrying the same feature so the next attempt starts from a known-good HEAD instead of an in-progress mess.
Pair with
`clad checkpoint <featureId>` — stamps the safety net rollback restores from. See `skills/checkpoint/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 Skillcheckpoint
Record a feature checkpoint event pinning the current git HEAD plus a spec digest, so a later rollback can restore the exact…
@qwerfunchInstall Skillclarify
Advance Cladding onboarding after the user answers a pending product question. Use the MCP prepare/apply flow, preserve the…
@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 rollback.
- Which coding agents can use rollback?
- rollback 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.