# Manage GitHub Issues with Structured Triage

Maintainers often lose time validating reports, finding duplicates, and writing consistent updates. This skill gives Claude, Codex, and Claude Code a repeatable workflow for triage, labels, responses, and PR coordination.

## Install

```bash
npx skillstore add c0ntr0lledcha0s/github-issues
```

## Metadata

- - Slug: c0ntr0lledcha0s-github-issues
- - Version: 1.0.0
- - Author: C0ntr0lledCha0s
- - GitHub username: C0ntr0lledCha0s
- - License: MIT
- - Repository: https://github.com/C0ntr0lledCha0s/logseq-template-graph/tree/main/.claude/skills/github-issues
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: external\_commands, network
- - Quality score: 71
- - Public page: https://skillstore.pages.dev/skills/c0ntr0lledcha0s-github-issues
- - Manifest: https://skillstore.pages.dev/api/skills/c0ntr0lledcha0s-github-issues/manifest

## Capabilities

- Guides issue validation by checking code, history, duplicates, and related reports.
- Suggests labels for issue type, priority, status, and project scope.
- Drafts maintainer responses for bugs, feature requests, questions, and duplicates.
- Creates implementation plans with affected files, dependencies, and next steps.
- Coordinates GitHub issue actions such as comments, closures, labels, and linked pull requests.
- Provides reusable examples for common Logseq Template Graph issue workflows.

## Use Cases

- Triage incoming bug reports: Validate reproduction details, check whether the bug is already fixed, and draft a clear maintainer response.
- Plan feature implementation: Assess a feature request, identify affected template files, map dependencies, and prepare a staged implementation plan.
- Clean up duplicate issues: Search existing issues, compare reports, add duplicate labels, and prepare closure comments with links to canonical issues.

## Prompt Templates

### Triage a new issue

```
Review issue #[number]. Validate whether it is a bug, feature request, question, or duplicate. Suggest labels and draft a response.
```

### Find duplicates and related work

```
Analyze issue #[number] against open and closed issues. Identify duplicates, related issues, blockers, and recommended relationship comments.
```

### Create an implementation plan

```
For issue #[number], validate the request, identify affected modules, list implementation tasks, estimate effort, and draft a progress comment.
```

### Coordinate issue to pull request

```
Prepare the issue lifecycle plan for #[number], including branch name, PR title, closing keywords, labels, release note text, and final issue comment.
```

## Limitations

- Focused on the Logseq Template Graph project and its labels, modules, and issue style.
- Requires GitHub CLI access for commands that read or modify GitHub issues.
- Does not verify command safety automatically before external state changes.
- Schema.org research and project validation may require current repository and network access.

## Best Practices

- Validate every report against code, history, and existing issues before responding.
- Review all gh and git commands before running actions that change repository state.
- Include evidence, relationships, labels, and next steps in each maintainer response.

## Anti Patterns

- Closing issues without explaining the validation result or linking supporting evidence.
- Running generated commands against a repository before reviewing their target issue numbers.
- Assuming a reporter is correct without checking code, documentation, or duplicate issues.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T19:27:48.292\+00:00
- - Summary: Static analysis produced many high-risk pattern matches, but targeted review found Markdown examples and maintainer workflow guidance rather than hidden executable code or malicious intent. The skill is publishable with a medium warning because it guides state-changing gh and git commands and includes limited external documentation lookup.

## Stats

- - Views: 335
- - Downloads: 4
- - Favorites: 0
- - Popularity score: 0