Individual skill
plan-version-history
DB-backed plan snapshots: when they are taken, how to list and inspect them, and what `restore-plan-version` preserves. Use when the user asks about plan history, undo, rollback, or restoring an earlier version of a plan.
templates/plan/.agents/skills/plan-version-history/SKILL.md
Source commit ff01b4009091c2140edb34d6f790ec64e7823356
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 7,637
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agents Repository topic
- ai Repository topic
- react Repository topic
- agent-native Repository topic
- typescript Repository topic
- agent-framework Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- framework Repository topic
- generative-ui Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,044 bytes
Read excerpt
# Plan Version History
- Plans keep DB-backed snapshots before meaningful authoring changes. Pure
comments, feedback replies, and comment status changes do not create history
snapshots.
- Use `list-plan-versions` to see saved snapshots for a plan, and
`get-plan-version` to inspect one full snapshot before recommending a
rollback.
- Use `restore-plan-version` only when the user asks to restore or roll back.
The current plan is snapshotted first with `Before restore`, so restore is
reversible. Restore preserves sharing, ownership, hosted publish metadata,
comments, and activity history; it restores the plan's authoring content and
legacy sections.