preserve
Commits the most recently approved development plan to the docs/plans/ directory.
Install
mkdir -p .claude/skills/preserve && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12298" && unzip -o skill.zip -d .claude/skills/preserve && rm skill.zipInstalls to .claude/skills/preserve
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Preserve the most recently approved plan to docs/plans/Key capabilities
- →Preserve the most recently approved plan to `docs/plans/`
- →Commit the plan locally with a `plan:` conventional commit
- →Exit plan mode before preserving the plan
- →Report the result of the preservation to the user
- →Use a POSIX bash shell for all commands
How it works
The skill takes the most recently approved plan, saves it to the `docs/plans/` directory, and then commits it locally using a `plan:` conventional commit. It requires a POSIX bash shell.
Inputs & outputs
When to use preserve
- →Documenting task implementation plans
- →Version controlling project milestones
- →Committing approved architectural designs
About preserve
Automatically captures and persists the active plan into the project's documentation folder. It strictly requires a POSIX bash shell and creates a conventional commit to track project trajectory.
Preserve the most recently approved plan to docs/plans/
When not to use it
- →When the user does not want to save the plan to `docs/plans/`
- →When the user does not want a `plan:` conventional commit
- →When the user wants to push the commit immediately
Limitations
- →Requires a POSIX bash shell
- →Commits the plan locally, does not push to remote
- →Only saves to the `docs/plans/` directory
How it compares
This skill automates the documentation and version control of approved plans with a specific commit message format, which is more structured than manually saving and committing a plan.
Compared to similar skills
preserve side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| preserve (this skill) | 0 | 4mo | Review | Beginner |
| tbd | 0 | 7mo | Review | Intermediate |
| session-handoff | 0 | 4mo | Review | Beginner |
| rankup-work-logging | 0 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
tbd
jlevy
|-
session-handoff
Maximumsoft-Co-LTD
Serialize mid-session context into a handoff doc so the next session (or engineer) can resume without cold-start
rankup-work-logging
antoniogagos
Work tracking + evidence logging for Rankup. Use when updating docs/work (CURRENT, ROADMAP, epics, log) and recording yarn validate evidence to close WPs/epics reproducibly.
handoff
hta218
Capture current work context for handoff to another agent/developer. Gathers git state, todos, and modified files into a structured handoff document saved to the related spec folder.
issue-to-requirement
1021ky
GitHub Issue の曖昧な要求を、このプロジェクトで実装可能な要件へ正規化する。機能分類、層別要件、実装スコープ、判定待ち項目を整理し、issue-to-plan へ渡す。
complete-task
Log2n-io
Complete work on a GitHub issue - close issue, update artifacts, prompt for doc updates