# Claim GitHub Issues Safely

Starting issue work requires validation, labels, comments, and local setup. This skill coordinates those steps for a specific GitHub issue number.

## Install

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

## Metadata

- Status: approved
- Slug: emasoft-ghe-claim
- Skillstore revision: r1
- Version status: missing
- Tree hash: 828ae190bdacb21ddadf0d0f63fbe9e23d37b286f6ea06ddde2e8457e1946bed
- Author: Emasoft
- GitHub username: Emasoft
- License: MIT
- Repository: https://github.com/Emasoft/ghe-marketplace/tree/main/plugins/ghe/skills/ghe-claim
- 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-claim
- Manifest: https://skillstore.pages.dev/api/skills/emasoft-ghe-claim/manifest

## Capabilities

- Requires a specific issue number before claiming work.
- Runs a phase validation step before changing issue state.
- Selects a thread manager based on dev, test, or review labels.
- Assigns the issue, adds in-progress, and removes ready.
- Posts a claim comment with session details.
- Creates a development worktree when DEV work requires it.

## Use Cases

- Begin Development Work: A developer claims a ready issue and creates the needed worktree before coding.
- Start Test Validation: A QA engineer claims a test-labeled issue after phase validation confirms prior work is complete.
- Coordinate Review Ownership: A maintainer claims a review issue and posts a clear session comment for the team.

## Prompt Templates

### Claim One Issue

```
Claim issue #201.
```

### Claim Development Work

```
Validate and claim issue #201 for development. Create a worktree if the issue is ready.
```

### Claim With Guardrails

```
Claim issue #201 only if the phase-gate passes. Report any blocker before changing assignment or labels.
```

### Run Full Claim Flow

```
For issue #201, run the claim flow, select the correct thread manager from labels, post the claim comment, and update memory.
```

## Limitations

- It depends on external GitHub and thread manager behavior.
- It can modify issue assignment, labels, comments, and local files.
- It requires valid repository access and an available issue.
- It does not finish or checkpoint work after a claim.

## Best Practices

- Use a clear issue number and confirm the repository context first.
- Review the phase-gate result before relying on the claim.
- Inspect generated comments before posting sensitive details to GitHub.

## Anti Patterns

- Do not use this skill to save progress on active work.
- Do not claim issues without ready labels or valid phase order.
- Do not let it write configuration files without explicit approval.

## Security Audit

- Audited at: 2026-07-06T12:25:05.191\+00:00
- Summary: Most external command detections were false positives caused by Markdown inline-code formatting, not executable backticks. Real concerns remain because the skill permits writes to ~/.claude and contains strong instruction-overriding language that can weaken agent safety. It also requires full reports to be posted to GitHub issue threads, which can disclose sensitive content.

## Stats

- Views: 197
- Downloads: 12
- Favorites: 0
- Popularity score: 0