Home
ghe-checkpoint
Emasoft/ghe-marketplace
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
...Expand allAbout 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.
IRON LAW: User Specifications Are Sacred
THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.
- Every word the user says is a specification - follow verbatim, no errors, no exceptions
- Never modify user specs without explicit discussion - if you identify a potential issue, STOP and discuss with the user FIRST
- Never take initiative to change specifications - your role is to implement, not to reinterpret
- If you see an error in the spec, you MUST:
- Stop immediately
- Explain the potential issue clearly
- Wait for user guidance before proceeding
- No silent "improvements" - what seems like an improvement to you may break the user's intent
Violation of this law invalidates all work produced.
Background Agent Boundaries
When running as a background agent, you may ONLY write to:
- The project directory and its subdirectories
- The parent directory (for sub-git projects)
- ~/.claude (for plugin/settings fixes)
- /tmp
Do NOT write outside these locations.
GHE_REPORTS Rule (MANDATORY)
ALL reports MUST be posted to BOTH locations:
- GitHub Issue Thread - Full report text (NOT just a link!)
- GHE_REPORTS/ - Same full report text (FLAT structure, no subfolders!)
Report naming: <TIMESTAMP>_<title or description>_(<AGENT>).mdTimestamp format: YYYYMMDDHHMMSSTimezone
ALL 11 agents write here: Athena, Hephaestus, Artemis, Hera, Themis, Mnemosyne, Hermes, Ares, Chronos, Argos Panoptes, Cerberus
REQUIREMENTS/ is SEPARATE - permanent design documents, never deleted.
Deletion Policy: DELETE ONLY when user EXPLICITLY orders deletion due to space constraints.
Settings Awareness
Respects .claude/ghe.local.md:
enabled: If false, skip checkpointserena_sync: If false, skip SERENA memory bank updatecheckpoint_interval_minutes: Used for reminder logic
GitHub Elements Checkpoint
Purpose: Save current work state to active thread. Does NOT change phases.
Precondition
- Must have an active (claimed, in-progress) thread
- If no active thread, use
ghe-claimfirst
When to Use
- Save progress during work
- Document milestones
- Record blockers
- Before ending session
- At meaningful state changes
How to Execute
Step 1: Find active thread
Check for issues assigned to @me with "in-progress" label.
If no active thread found:
- Inform user
- Suggest using
ghe-claimto start work
Step 2: Gather current state
Collect:
- Work log (what was done since last checkpoint)
- Completed tasks
- In-progress tasks
- Pending tasks
- Files changed
- Commits made
- Current branch
- Blockers (if any)
- Next action
Step 3: Post checkpoint
Spawn appropriate thread manager based on thread type:
dev→ dev-thread-managertest→ test-thread-managerreview→ review-thread-manager
The thread manager will post formatted checkpoint to issue.
Step 4: Sync memory
Spawn memory-sync agent to update activeContext.md.
Checkpoint Format
## [<TYPE> Session N] DATE TIME UTC - @me### Work Log- [HH:MM] Action 1- [HH:MM] Action 2### State Snapshot#### Thread Type<dev | test | review>#### Completed- [x] Task 1#### In Progress- [ ] Task 2 (N% complete)#### Pending- [ ] Task 3#### Files Changed| File | Changes |#### Commits| Hash | Message |#### Branch`feature/branch-name`#### Blockers[None | List]#### Next Action[Specific next step]### Scope Reminder[Phase-specific abilities and limits]
Output
Confirmation that:
- Checkpoint posted to issue
- Memory bank updated
Key Differentiator
This skill SAVES progress without changing phases. To COMPLETE current phase and MOVE to next, use ghe-transition instead.
Install ghe-checkpoint
Download and extract the skill files to your .claude/skills/ directory.
Download ZIPClone the repository and copy the skill files to your project.
git clone https://github.com/Emasoft/ghe-marketplace/blob/main/plugins/ghe/skills/ghe-checkpoint/SKILL.md # Copy SKILL.md to your .claude/skills/ directory
Copy
