/devkit.lra.checkpoint
Create a checkpoint - commit changes, update progress log, leave clean state for next session
$ npx -y skills add giuseppe-trisciuoglio/developer-kit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/devkit.lra.checkpoint
Context preview
What this command does when you run it.
Create a checkpoint - commit changes, update progress log, leave clean state for next session
Command definition
devkit.lra.checkpoint.mddescription: Create a checkpoint - commit changes, update progress log, leave clean state for next session
allowed-tools: Read, Write, Edit, Bash(git:*)
argument-hint: "[summary-of-work-done]"
Long-Running Agent - Create Checkpoint
Create a checkpoint at the end of a coding session. This ensures the next agent can pick up where you left off.
Summary of Work Done
$ARGUMENTS
Checkpoint Protocol
Execute these steps to leave the environment in a clean state:
Step 1: Verify Clean State
Before creating a checkpoint, ensure:
1. **No broken tests**: Run the test suite 2. **App runs**: Start the dev server and verify basic functionality 3. **No syntax errors**: Code compiles/lints without errors
If there are issues, FIX THEM before proceeding.
Step 2: Stage and Commit Changes
Review what changed:
git status
git diff --stat
Create a descriptive commit:
git add -A
git commit -m "feat: [brief description of main change]
- Detail 1
- Detail 2
- Detail 3
Session checkpoint - app in working state"
Step 3: Update Progress Log
Append to `.lra/progress.txt`:
---
### Session [N] - [Date] - [Brief Title]
**Feature Worked On**: [Feature ID] - [Description]
**Accomplished**:
- [What was done]
- [What was done]
**Status**: [Complete / In Progress / Blocked]
**Notes for Next Session**:
- [Important context]
- [Any gotchas or warnings]
- [Suggested next steps]
**Commits This Session**:
- [commit hash] - [message]
Step 4: Final Git Status
Confirm everything is committed:
git status
git log --oneline -5
Output
Provide a session summary:
═══════════════════════════════════════════════════════════
SESSION CHECKPOINT
═══════════════════════════════════════════════════════════
📋 Session Summary
Feature: F012 - User authentication flow
Status: COMPLETE ✓
📝 Changes Made
- Implemented login endpoint
- Added JWT token generation
- Created auth middleware
- Added unit tests for auth service
📊 Project Progress
Features: 12/42 completed (29%)
By Priority:
- Critical: 4/5 done
- High: 6/15 done
- Medium: 2/18 done
- Low: 0/4 done
💾 Git Status
Commit: abc1234 - feat(auth): implement user login flow
Branch: main
Working tree: clean
📌 Notes for Next Agent
- Auth is working, next implement password reset
- Redis session store not yet configured
- See .lra/progress.txt for full history
═══════════════════════════════════════════════════════════
READY FOR NEXT SESSION
═══════════════════════════════════════════════════════════Important
- **NEVER leave the codebase in a broken state**
- **ALWAYS update progress.txt with context for the next agent**
- **ALWAYS commit with descriptive messages**
- This checkpoint allows context window transitions to be seamless
Execution Instructions
**Agent Selection**: To execute this LRA task, use the following approach:
- Primary: Use `general-purpose` agent with task management and state persistence capabilities
- Or use `plan` agent for complex multi-step workflows
Read more
description: Create a checkpoint - commit changes, update progress log, leave clean state for next session allowed-tools: Read, Write, Edit, Bash(git:*) argument-hint: "[summary-of-work-done]"
Long-Running Agent - Create Checkpoint
Create a checkpoint at the end of a coding session. This ensures the next agent can pick up where you left off.
Summary of Work Done
$ARGUMENTS
Checkpoint Protocol
Execute these steps to leave the environment in a clean state:
Step 1: Verify Clean State
Before creating a checkpoint, ensure:
1. **No broken tests**: Run the test suite 2. **App runs**: Start the dev server and verify basic functionality 3. **No syntax errors**: Code compiles/lints without errors
If there are issues, FIX THEM before proceeding.
Step 2: Stage and Commit Changes
Review what changed:
git status git diff --stat
Create a descriptive commit:
git add -A git commit -m "feat: [brief description of main change] - Detail 1 - Detail 2 - Detail 3 Session checkpoint - app in working state"
Step 3: Update Progress Log
Append to `.lra/progress.txt`:
--- ### Session [N] - [Date] - [Brief Title] **Feature Worked On**: [Feature ID] - [Description] **Accomplished**: - [What was done] - [What was done] **Status**: [Complete / In Progress / Blocked] **Notes for Next Session**: - [Important context] - [Any gotchas or warnings] - [Suggested next steps] **Commits This Session**: - [commit hash] - [message]
Step 4: Final Git Status
Confirm everything is committed:
git status git log --oneline -5
Output
Provide a session summary:
═══════════════════════════════════════════════════════════
SESSION CHECKPOINT
═══════════════════════════════════════════════════════════
📋 Session Summary
Feature: F012 - User authentication flow
Status: COMPLETE ✓
📝 Changes Made
- Implemented login endpoint
- Added JWT token generation
- Created auth middleware
- Added unit tests for auth service
📊 Project Progress
Features: 12/42 completed (29%)
By Priority:
- Critical: 4/5 done
- High: 6/15 done
- Medium: 2/18 done
- Low: 0/4 done
💾 Git Status
Commit: abc1234 - feat(auth): implement user login flow
Branch: main
Working tree: clean
📌 Notes for Next Agent
- Auth is working, next implement password reset
- Redis session store not yet configured
- See .lra/progress.txt for full history
═══════════════════════════════════════════════════════════
READY FOR NEXT SESSION
═══════════════════════════════════════════════════════════Important
- **NEVER leave the codebase in a broken state**
- **ALWAYS update progress.txt with context for the next agent**
- **ALWAYS commit with descriptive messages**
- This checkpoint allows context window transitions to be seamless
Execution Instructions
**Agent Selection**: To execute this LRA task, use the following approach:
- Primary: Use `general-purpose` agent with task management and state persistence capabilities
- Or use `plan` agent for complex multi-step workflows
Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI.
Repo: giuseppe-trisciuoglio/developer-kit
Other commands on developer-kit.
- /devkit.prompt-optimize
Provides expert prompt optimization using advanced techniques (CoT, few-shot, constitutional AI) for LLM performance enhancement. Use when you need to improve prompt quality or optimize LLM interactions.
Open command - /devkit.feature-development
Provides guided feature development capability with codebase understanding and architecture focus. Use when implementing a new feature from scratch.
Open command - /devkit.fix-debugging
Provides guided bug fixing and debugging capability with systematic root cause analysis. Use when encountering bugs, errors, or unexpected behavior.
Open command - /devkit.github.create-pr
Creates a GitHub pull request with branch creation, commits, and detailed description. Use when you need to submit changes for review.
Open command - /devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
Open command - /devkit.refactor
Provides guided code refactoring capability with deep codebase understanding, compatibility options, and comprehensive verification. Use when restructuring or improving existing code.
Open command

