# Coordinate GitHub Issue Workflows

Long AI tasks lose context and coordination across sessions. This skill uses GitHub Issues, checkpoints, and worktrees to preserve state and guide phase transitions.

## Install

```bash
npx skillstore add emasoft/github-elements-tracking
```

## Metadata

- Status: approved
- Slug: emasoft-github-elements-tracking
- Skillstore revision: r1
- Version status: missing
- Tree hash: f7cf8640c57d92421aa591f30a73f3040016d2b5125cadef03c02d76d052d6b5
- Author: Emasoft
- GitHub username: Emasoft
- License: MIT
- Repository: https://github.com/Emasoft/ghe-marketplace/tree/main/plugins/ghe/skills/github-elements-tracking
- Ref: 30c73eac2afe762f6aa9c4553158769369d47351
- 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, env\_access, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/emasoft-github-elements-tracking
- Manifest: https://skillstore.pages.dev/api/skills/emasoft-github-elements-tracking/manifest

## Capabilities

- Defines DEV, TEST, and REVIEW issue thread protocols for staged work.
- Uses GitHub issue comments as persistent checkpoints across sessions.
- Provides worktree guidance for branch isolation during issue work.
- Includes templates for claims, progress updates, reports, and transitions.
- Describes optional SERENA memory-bank synchronization for larger context.
- Documents GitHub Actions enforcement examples for workflow validation.

## Use Cases

- Recover Long Tasks: Resume work after context loss by reading issue checkpoints and phase status.
- Coordinate Agent Phases: Separate development, testing, and review responsibilities across GitHub issue threads.
- Audit Feature History: Trace claims, decisions, test results, and review outcomes from issue comments.

## Prompt Templates

### Start Tracking

```
Create a GitHub issue workflow for this feature. Define the phase, scope, acceptance criteria, and first checkpoint.
```

### Claim Work

```
Claim issue <number>, identify the active phase, declare the files in scope, and post a starting checkpoint.
```

### Recover Session

```
Read issue <number> and reconstruct the current state, blockers, completed work, and next action.
```

### Coordinate Epic

```
Review the epic issue, map active DEV, TEST, and REVIEW threads, find conflicts, and propose the next wave plan.
```

## Limitations

- Requires GitHub CLI access and an authenticated repository context.
- Many workflows are documented procedures, not packaged executable tooling.
- Automation snippets need local security review before installation.
- GitHub issue and comment size limits still apply.

## Best Practices

- Confirm repository, issue number, and phase before running GitHub CLI commands.
- Post short checkpoints at meaningful state changes, not every minor edit.
- Review automation snippets and token permissions before installing enforcement workflows.

## Anti Patterns

- Do not merge branches before a recorded REVIEW pass.
- Do not treat issue comments as optional when they hold project memory.
- Do not run setup scripts from the skill without inspecting the commands first.

## Security Audit

- Audited at: 2026-07-05T16:05:18.543\+00:00
- Summary: Most static hits are documentation artifacts, especially Markdown code spans, example links, and workflow prose. Confirmed risks remain because the skill directs agents to run shell and GitHub CLI commands, write parent worktree paths, modify hidden Claude configuration, install an external MCP package, and install GitHub automation with write permissions.

## Stats

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