ghe-checkpoint
POST a progress checkpoint to the CURRENTLY ACTIVE thread. Saves work state without changing phases. Requires an already-claimed in-progress thread.USE THIS SKILL WHEN:- User says "post a checkpoint" or "save my progress"- User says "update the issue" or "record current state"- User says "checkpoint" or "save checkpoint"- User completed a milestone and wants to record it- User encountered a blocker and wants to document it- User is about to take a break and wants to save state- Meaningful state
Security Assessment
About ghe-checkpoint
The `ghe-checkpoint` skill allows users to save their current progress in an active GitHub issue thread without advancing project phases. It is designed to provide a seamless way to record work state, milestones, and blockers, ensuring that ongoing work is preserved even if the user needs to pause or take a break. This skill addresses the challenge of losing track of incremental progress during development or project management, making it easier to maintain accurate records of work in real-time.
The main capabilities of this skill include posting a progress checkpoint to the currently active thread, recording milestones, documenting blockers, and preserving meaningful state changes. It strictly requires an already-claimed in-progress thread and respects local configuration settings such as `.claude/ghe.local.md`. The skill does not change the phase of the project or start new tasks, focusing solely on capturing the current work state. Additionally, it follows strict reporting rules, ensuring that all updates are saved both in the GitHub issue thread and in the local `GHE_REPORTS` directory for full traceability.
`ghe-checkpoint` is primarily intended for developers, project managers, and technical teams who use GitHub for issue tracking and task management. Typical use cases include saving progress during development sessions, documenting the completion of milestones, recording blockers that require attention, and maintaining up-to-date records before pausing work. It is especially useful in collaborative environments where multiple team members need visibility into ongoing work and where maintaining accurate project history is critical.
FAQ
When should I use the `ghe-checkpoint` skill?
Use this skill whenever you want to save progress in an active thread, document milestones, record blockers, or preserve meaningful state changes during work. It is also useful before taking a break to ensure work state is saved.
Can I use `ghe-checkpoint` without an active thread?
No, the skill requires an already-claimed in-progress thread. If no active thread exists, you must first use the `ghe-claim` skill to claim one.
Does `ghe-checkpoint` change the project phase?
No, this skill only saves the current work state without advancing project phases. To move to the next phase, you should use the `ghe-transition` skill.
How does `ghe-checkpoint` handle reports?
All checkpoints are posted both to the GitHub issue thread and saved locally in the `GHE_REPORTS/` directory as a flat structure. Reports include the full text of the checkpoint, not just links.
Can I disable checkpointing or syncing with memory banks?
Yes, the skill respects local settings in `.claude/ghe.local.md`. If `enabled` is false, checkpoints are skipped, and if `serena_sync` is false, updates to the SERENA memory bank are skipped.
Install ghe-checkpoint
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
Emasoft/ghe-marketplace