# 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 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.

## Facts
- Page: https://tashan.sh/capability/skill-qwerfunch-checkpoint
- tashan id: skill:qwerfunch/checkpoint
- Source: https://github.com/qwerfunch/cladding
- Type: skill
- Category: devtools
- tashan score: 51.0 / 100
- Adoption: 14.0
- Upkeep: 99.0
- Freshness: 98.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- License: MIT
- Official: no

## Install

```sh
cp -r checkpoint ~/.claude/skills/
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-08-15 by tashan (https://tashan.sh) from public evidence. Scorer s5.