name	continue-crash
version	1.0.0
description	Continues after a session crash while working on a task
disable-model-invocation	true
allowed-tools	Bash, Glob, Grep, Read, TodoWrite

Context

Git status: !git status --porcelain 2>/dev/null | head -20 || echo "NOT_IN_GIT"
Recent commits: !git log --oneline -5 2>/dev/null || echo "NO_COMMITS"
Modified files: !git diff --name-only 2>/dev/null | head -10 || echo "NONE"
Current branch: !git branch --show-current 2>/dev/null || echo "UNKNOWN"
TODO files: !sh -c 'COMMON=$(git rev-parse --path-format=absolute --git-common-dir 2>/dev/null); PROJECT_ROOT=$(dirname "$COMMON" 2>/dev/null); if [ -n "$PROJECT_ROOT" ] && [ "$PROJECT_ROOT" != "." ]; then ls -la "$PROJECT_ROOT"/PLAN__*.md "$PROJECT_ROOT"/TODO.md 2>/dev/null || echo "No TODO files found"; else ls -la PLAN__*.md TODO.md 2>/dev/null || echo "No TODO files found"; fi'

Continue After Crash

Our session crashed. Use the context above to recover and continue where we left off.

Recovery Process

Analyze context from pre-executed commands above:
- Review git status to see uncommitted work
- Check recent commits to understand what was completed
- Look for TODO/PLAN files documenting the task
Reconstruct and resume:
- Identify the task from the evidence
- Create or update TODO list based on actual progress
- Fix any test failures before continuing
- Continue from the interruption point

Important

Base reconstruction only on the evidence provided in Context
If context is unclear from the data above, ask for clarification
Don't duplicate completed work - verify what's done in git history
Maintain the original task direction and intent

Resume work from where it was interrupted.

Más de este repositorio

mismo repositorio

code-reviewer

wpfleger96/ai-agent-rules

Performs thorough code review on local changes or PRs. Use this skill proactively after implementing code changes to catch issues before commit/push. Also use when reviewing PRs from other engineers.

2026-07-154

handoff

wpfleger96/ai-agent-rules

Generate a portable session handoff document (task, decisions, state, next steps) as a single copy-pasteable markdown block for resuming on another device or terminal.

2026-07-054

agents-md

wpfleger96/ai-agent-rules

Create or update AGENTS.md with repo-specific patterns, conventions, commands, and gotchas for LLM coding agents. Use after implementing features that introduce new patterns worth documenting.

2026-07-044

crossfire

wpfleger96/ai-agent-rules

Get multi-model perspectives (Codex + Gemini) on any work product. Use at any development stage — planning, design, implementation, testing — to catch blind spots the primary agent might miss.

2026-07-044

dev-docs

wpfleger96/ai-agent-rules

Creates or updates PLAN.md based on session - auto-detects create vs update mode

2026-07-044

doc-writer

wpfleger96/ai-agent-rules

Write, update, or review documentation (README, ARCHITECTURE.md, API docs, guides). Use after implementing features to document new APIs, CLI commands, or behavior changes.

2026-07-044

name	continue-crash
version	1.0.0
description	Continues after a session crash while working on a task
disable-model-invocation	true
allowed-tools	Bash, Glob, Grep, Read, TodoWrite

Context

Git status: !git status --porcelain 2>/dev/null | head -20 || echo "NOT_IN_GIT"
Recent commits: !git log --oneline -5 2>/dev/null || echo "NO_COMMITS"
Modified files: !git diff --name-only 2>/dev/null | head -10 || echo "NONE"
Current branch: !git branch --show-current 2>/dev/null || echo "UNKNOWN"
TODO files: !sh -c 'COMMON=$(git rev-parse --path-format=absolute --git-common-dir 2>/dev/null); PROJECT_ROOT=$(dirname "$COMMON" 2>/dev/null); if [ -n "$PROJECT_ROOT" ] && [ "$PROJECT_ROOT" != "." ]; then ls -la "$PROJECT_ROOT"/PLAN__*.md "$PROJECT_ROOT"/TODO.md 2>/dev/null || echo "No TODO files found"; else ls -la PLAN__*.md TODO.md 2>/dev/null || echo "No TODO files found"; fi'

Continue After Crash

Our session crashed. Use the context above to recover and continue where we left off.

Recovery Process

Analyze context from pre-executed commands above:
- Review git status to see uncommitted work
- Check recent commits to understand what was completed
- Look for TODO/PLAN files documenting the task
Reconstruct and resume:
- Identify the task from the evidence
- Create or update TODO list based on actual progress
- Fix any test failures before continuing
- Continue from the interruption point

Important

Base reconstruction only on the evidence provided in Context
If context is unclear from the data above, ask for clarification
Don't duplicate completed work - verify what's done in git history
Maintain the original task direction and intent

Resume work from where it was interrupted.