- Home
- Skills
- Petekp
- Claude Code Setup
- Bootstrap
bootstrap_skill
- Shell
17
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill petekp/claude-code-setup --skill bootstrap- SKILL.md5.7 KB
Overview
This skill generates a focused bootstrap prompt that captures the essential state of a Claude Code session so work can continue seamlessly in a fresh session. It summarizes objectives, decisions, progress, gotchas, and next steps into a compact handoff document. The output is saved to a timestamped file and optionally copied to the clipboard for immediate use.
How this skill works
The skill analyzes the active conversation and repository state, selects only the context needed for continuation, and formats a concise markdown bootstrap prompt. It can run helper scripts to gather git status and copy the final file, then writes the handoff to .claude/handoffs/{project-name}-{YYYYMMDD-HHMMSS}.md. The prompt emphasizes rationale, blockers, and concrete next actions rather than dumping raw logs.
When to use it
- You want to capture the current session so another Claude Code session can resume later
- You need a concise handoff before closing a session or switching machines
- You want to save decisions, gotchas, and the critical path for future work
- You need to create a session summary for teammates or automated continuation
- You plan to pause development and resume with minimal re-orientation
Best practices
- Include only context that matters for continuation: objectives, blockers, and key decisions
- Run the git-state script before generating the bootstrap to capture branch and diffs
- Prioritize next steps and give exact commands or files to open for quick resume
- Document non-obvious rationale so future sessions avoid re-litigating choices
- Keep the handoff short—omit resolved dead-ends and routine operations
Example use cases
- Finish an incomplete feature in a fresh Claude Code session using the bootstrap file
- Hand off progress to a teammate with a single markdown file outlining next actions
- Pause a debugging session and capture intermediate findings, hypotheses, and commands
- Create a reproducible resumption point before rebasing or switching branches
- Produce a short session summary for project management or QA to act on
FAQ
It typically includes Context, Session Summary, Current State, Key Files, Decisions, Gotchas, Next Steps, and Resume Instructions; omit irrelevant sections.
How does it avoid dumping everything?
The skill applies intelligent context selection: keep only items that matter for continuation, emphasize decisions, blockers, and unique pitfalls.
Where is the handoff file saved?
By default it writes to .claude/handoffs/{project-name}-{YYYYMMDD-HHMMSS}.md and can copy the content to the clipboard.