github-issue-hierarchy
/github-issue-hierarchy
Create GitHub issues with optional parent/sub-issue relationships and organization issue types. Use when the user asks to create, link, or retag GitHub issues, especially when they mention a parent issue, sub-issues, tasks, bugs, epics, or cross-repo issue hierarchy.
- Author
- TechDufus ↗
- Repository
- dotfiles ↗
- Licence
- Apache-2.0
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/gh-issue-hierarchy.sh
What it does and when to use it
Create GitHub issues with optional parent/sub-issue relationships and organization issue types. Use when the user asks to create, link, or retag GitHub issues, especially when they mention a parent issue, sub-issues, tasks, bugs, epics, or cross-repo issue hierarchy.
Original author description
Create GitHub issues with optional parent/sub-issue relationships and organization issue types. Use when the user asks to create, link, or retag GitHub issues, especially when they mention a parent issue, sub-issues, tasks, bugs, epics, or cross-repo issue hierarchy.
How it works
- Defaults
- Workflow
- Commands
- Notes
SKILL.md preview
---
name: github-issue-hierarchy
description: Create GitHub issues with optional parent/sub-issue relationships and organization issue types. Use when the user asks to create, link, or retag GitHub issues, especially when they mention a parent issue, sub-issues, tasks, bugs, epics, or cross-repo issue hierarchy.
metadata:
short-description: Hierarchical GitHub issues
---
# GitHub Issue Hierarchy
Use this skill when issue creation needs hierarchy or issue types, not just a plain `gh issue create`.
## Defaults
- If the user wants a plain issue with no parent and no issue type, `gh issue create` is enough.
- If the user gives a parent issue, asks for a sub-issue, or wants an issue type like `Task` or `Epic`,
use the bundled helper: [scripts/gh-issue-hierarchy.sh](scripts/gh-issue-hierarchy.sh).
- Do not invent a parent issue. Link only when the user or current task context identifies one.
## Workflow
1. Decide the repository.
- Prefer an explicit repo from the user.
- Otherwise use the current checkout or `GITHUB_REPOSITORY`.
2. Write the issue title and body from the current task context.
3. Check issue-type support when a type matters:
- Run `scripts/gh-issue-hierarchy.sh issue-types --repo owner/repo`
- If `supported` is `false`, the repo does not expose organization issue types. Do not force one.
- If `lookup_error` is present, treat that as an org-level permission or feature-availability failure and tell the user plainly.
- If `supported` is `true`, match the requested type name case-insensitively against the returned list.
4. Create the issue:
- If a parent or issue type is involved, use the helper's `create` subcommand so the issue is created
with `parentIssueId` and `issueTypeId` in one call.
5. Update existing issues when needed:
- Use `link` to attach an existing child to a parent.
- Use `set-type` to change an existing issue's type.
## Commands
Check issue-type support for a repo:
```bash
modules/codex/skills/github-issue-hierarchy/scripts/gh-issue-hierarchy.sh issue-types \
--repo owner/repo
```
Create a child issue with an org issue type:
```bash
modules/codex/skills/github-issue-hierarchy/scripts/gh-issue-hierarchy.sh create \
--repo owner/repo \
--title "Implement session refresh" \
--body-file /tmp/issue-body.md \
--parent "owner/repo#123" \
--type Task
```
Link an existing issue as a sub-issue:
```bash
modules/codex/skills/github-issue-hierarchy/scripts/gh-issue-hierarchy.sh link \
--parent "owner/repo#123" \
--child "owner/repo#456"
```
Reassign a child that already has a parent:
```bash
modules/codex/skills/github-issue-hierarchy/scripts/gh-issue-hierarchy.sh link \
--parent "owner/repo#123" \
--child "owner/repo#456" \
--replace-parent
```
Change an existing issue type:
```bash
modules/codex/skills/github-issue-hierarchy/scripts/gh-issue-hierarchy.sh set-type \
"owner/repo#456" \
--type Bug
```
## Notes
- The current `gh issue create` and `gh issue edit` CLI surface still has no issue-type flag, so use the
helper whenever issue types are relevant.
- GitHub documents REST sub-issue endpoints under `/repos/{owner}/{repo}/issues/{issue_number}/sub_issues`,
but the helper uses GraphQL for create and link flows because `createIssue`, `addSubIssue`, and
`updateIssueIssueType` compose cleanly with global node IDs.
- Organization issue types are discovered from the org-scoped REST endpoint. Personal repositories should
be treated as having no issue-type support.
- Querying org issue types is permission-sensitive. A `supported: false` result with `lookup_error` usually
means the token cannot read org issue-type settings, not necessarily that the repo can never use them.
- If `lookup_error` mentions `admin:org`, the current `gh` auth is too weak to discover type IDs by name.
Tell the user and either skip the type or have them run `gh auth refresh -h github.com -s admin:org`.
Files in this package (2)
- SKILL.md 4 KB
- scripts/gh-issue-hierarchy.sh 11 KB
Versions
The database has no other skills named github-issue-hierarchy.
Database snapshot: 13.11.2026 · package version 04dd2450f363 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100create-issue
Turn a feature request or a finished implementation plan into GitHub issues grounded in the real code, then create them with the gh CLI. A plan with several tasks becomes one parent issue with one sub-issue per task. Use when the user says "create an issue", "file this as… - 100git-issue-hierarchy
GitHub sub-issues and blocked_by/blocking links. Use when breaking an issue into sub-tasks, checking parent progress, or viewing a dependency graph. - 100create-github-issue
Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue. - 87github-issues
**UNIVERSAL TRIGGER**: Use when user mentions GitHub issue URL or asks to read/work with GitHub issues. **Default handler**: Bare GitHub issue URL without action verb -> github-issues (read mode). If user sends just a URL like "https://github.com/org/repo/issues/42" with no… - 100managing-issues
Use when the requested outcome is reading, drafting, creating, or surgically updating GitHub or Linear issue records; changing their native parent, sub-issue, or blocker relationships and assessing readiness; checking completion against Verification evidence; or reversibly… - 100github-issue-model
This skill should be used when working with GitHub's issue data model — issue types, sub-issues, dependencies, labels, milestones, issue forms and templates, and the community health files that configure them.