# Record GitHub Issue Checkpoints

Long development sessions can lose state across tools, agents, and handoffs. This skill records a structured checkpoint in the active GitHub Issue thread and GHE_REPORTS.

## Install

```bash
npx skillstore add emasoft/ghe-checkpoint
```

## Metadata

- Status: approved
- Slug: emasoft-ghe-checkpoint
- Skillstore revision: r1
- Version status: missing
- Tree hash: fb88c401f6ff13a347f80c95f9f07e25da3a171e8cf42d6a359054148b9f3126
- Author: Emasoft
- GitHub username: Emasoft
- License: MIT
- Repository: https://github.com/Emasoft/ghe-marketplace/tree/main/plugins/ghe/skills/ghe-checkpoint
- Ref: 72d5025b022c77f7a51bdf5c1637c689c80e89d1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/emasoft-ghe-checkpoint
- Manifest: https://skillstore.pages.dev/api/skills/emasoft-ghe-checkpoint/manifest

## Capabilities

- Checks for an active claimed issue before posting a checkpoint.
- Collects completed tasks, pending tasks, files changed, commits, branch, blockers, and next action.
- Chooses a dev, test, or review thread manager from the thread type.
- Requires full report text in both the GitHub Issue thread and GHE\_REPORTS.
- Updates activeContext.md through the memory-sync agent when enabled.
- Keeps the current workflow phase unchanged.

## Use Cases

- Developer Session Handoff: Capture completed work, open tasks, branch state, and next action before another agent or teammate continues.
- Test Run Progress Log: Record blockers, files changed, and pending validation while a test issue stays in progress.
- Review Workflow Checkpoint: Post a concise state snapshot for reviewers without closing the current review phase.

## Prompt Templates

### Save Current Progress

```
Use ghe-checkpoint to record what I finished, what is still pending, current blockers, and the next action.
```

### Checkpoint Before Session End

```
Create a checkpoint for the active GitHub Issue before this session ends. Include changed files, commits, branch, blockers, and next steps.
```

### Document a Blocker

```
Post a checkpoint that focuses on the current blocker, evidence gathered, attempted fixes, affected files, and the decision needed.
```

### Prepare Cross-Agent Handoff

```
Build a detailed checkpoint for the active thread. Separate completed, in-progress, and pending work, then sync the memory context.
```

## Limitations

- Requires an existing claimed issue with an in-progress label.
- Depends on companion thread-manager and memory-sync agents.
- Does not complete phases or move work to another workflow state.
- May expose project details if checkpoint text contains sensitive information.

## Best Practices

- Run the skill only after a GitHub Issue is claimed and labeled in progress.
- Include concrete file names, commit hashes, blockers, and next actions in each checkpoint.
- Review sensitive details before posting checkpoint text to a GitHub Issue.

## Anti Patterns

- Do not use this skill to close a phase or move work to the next phase.
- Do not run it when no active issue thread is assigned to you.
- Do not post secrets, private credentials, or unreleased business details in checkpoints.

## Security Audit

- Audited at: 2026-07-06T12:21:21.457\+00:00
- Summary: Most static external-command hits are false positives from Markdown inline code and fences. The home-directory finding is confirmed because the skill allows writes to ~/.claude. Semantic review also found instruction-hierarchy override language that should be removed before publication.

## Stats

- Views: 229
- Downloads: 9
- Favorites: 0
- Popularity score: 0