What is the difference between ghe-checkpoint and ghe-transition?

ghe-checkpoint saves your work state within the current phase without changing it, while ghe-transition completes the current phase and moves the project to the next stage (e.g., from dev to test).

Does this skill update Claude's internal memory?

Yes, it automatically spawns a memory-sync agent to update the activeContext.md file, ensuring Claude's internal state matches the GitHub thread.

Can I use this to document project blockers?

Yes, the checkpoint format includes a specific section for blockers, making it an ideal way to record issues that are preventing further progress.

Where are the progress reports stored?

Reports are posted as comments on the GitHub Issue thread and also saved locally in the GHE_REPORTS/ directory with a unique timestamp.

Do I need an active GitHub issue to use this skill?

Yes, you must have an active, claimed thread in progress. If no thread is active, you should use the ghe-claim skill first.

GitHub Elements Checkpoint

Name: GitHub Elements Checkpoint
Author: Emasoft

byEmasoft

•

Collaboration Tools

Saves current development state and progress updates directly to active GitHub issue threads for persistent project tracking.

About

The ghe-checkpoint skill enables Claude Code to maintain a persistent and transparent record of work by posting detailed state snapshots to GitHub issues. It captures the current work log, completed tasks, changed files, and blockers without advancing the project phase. This is essential for maintaining context across sessions, informing team members of real-time progress, and ensuring that the local memory bank stays synchronized with the actual state of the repository.

Key Features

Detailed state snapshots including tasks, files, and commits
4 GitHub stars
Persistent progress recording to GitHub Issue threads
Dedicated sections for documenting milestones and blockers
Compliance with GHE_REPORTS mandatory reporting standards
Automatic synchronization with Claude's local memory bank

Use Cases

Recording the completion of a specific milestone within a development or testing phase.
Providing a detailed status update and state capture when encountering a technical blocker.
Documenting progress before ending a session to ensure context is preserved for the next start.

About

Key Features

Detailed state snapshots including tasks, files, and commits
4 GitHub stars
Persistent progress recording to GitHub Issue threads
Dedicated sections for documenting milestones and blockers
Compliance with GHE_REPORTS mandatory reporting standards
Automatic synchronization with Claude's local memory bank

Use Cases

Recording the completion of a specific milestone within a development or testing phase.
Providing a detailed status update and state capture when encountering a technical blocker.
Documenting progress before ending a session to ensure context is preserved for the next start.