Menu
File a new GitHub issue with duplicate search, scope decision, label discovery, and preview before posting. Prevents fragmented or silently-filed issues.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Close a GitHub issue with discipline — resolved, superseded, or duplicate. Pre-flights body + comments, migrates substance before destroying context, cross-links both directions.
Restructure the topology of GitHub issues — split one into many focused replacements, or merge multiple into one keeper. Migrates substance and cross-links before closing anything.
Update an existing GitHub issue — edit body, post a comment, retag, or reopen. Pre-flights body + comments; acknowledges stale framing instead of silently rewriting.
Review and address PR feedback using 6-dimensional code review
Structured code review using 6 dimensions. Works with or without the code-reviewer agent.
Create conventional commits with quality gates and validation
| name | issue-create |
| description | File a new GitHub issue with duplicate search, scope decision, label discovery, and preview before posting. Prevents fragmented or silently-filed issues. |
| allowed-tools | Bash(gh issue *), Bash(gh search *), Bash(gh label *), Bash(gh repo *), Read, Edit, Write |
Search for duplicates, decide scope, pick labels, preview the body to the user, then file.
File new issues without fragmenting discussion or losing scope clarity.
gh issue create.gh label list. Never invent labels.gh CLI authenticated; repo accessible.gh search issues "<keywords>" --repo <owner>/<repo>
gh issue list --repo <owner>/<repo> --search "<keywords>" --state all
If a relevant issue exists, comment there instead and stop. See DETAIL: Duplicate Handling.
Focused ("fix X in file Y") vs umbrella (cross-cutting, with checkboxes). Prefer focused unless the work spans multiple PRs.
gh label list --repo <owner>/<repo>
Apply: kind (bug / enhancement / chore), area (mcp-server / client / etc.), priority (p0/p1/p2/p3).
Include: context, current behavior, expected behavior, file:line refs, cross-links to related issues / PRs.
Show title + body + labels. Wait for confirmation.
gh issue create --repo <owner>/<repo> --title "..." --body "..." --label "..."
Print the URL.
When gh search surfaces a candidate:
Fragmenting discussion across near-duplicates is worse than over-linking.
Focused — one fix, one file or one tight area, one PR closes it. Default.
Umbrella — cross-cutting, multiple PRs, tracked via checkboxes. Use when:
When in doubt, file focused. Splitting an umbrella later is cheap; merging focused issues later is also cheap (/issue-restructure merge).
If the repo has no label matching the area / kind / priority:
area:* label exists yet — suggest creating one."gh label create from this skill — that's a repo-config decision for the maintainer./issue-close — Close an issue (resolved / superseded / duplicate)./issue-update — Edit body / labels, reopen, comment./issue-restructure — Split one issue into many, or merge many into one./harness-issue — File upstream against harness-kit specifically.