gh-sub-issue
GitHub CLI の extension を使って `gh sub-issue` コマンド経由で Sub Issue を操作する Skill. You can connect existing issues as sub-issues to a parent issue,create new issues directly linked to a parent, unlink sub-issues from their parent without deleting the issues, and view all sub-issues connected to a parent issue.
Best use case
gh-sub-issue is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
GitHub CLI の extension を使って `gh sub-issue` コマンド経由で Sub Issue を操作する Skill. You can connect existing issues as sub-issues to a parent issue,create new issues directly linked to a parent, unlink sub-issues from their parent without deleting the issues, and view all sub-issues connected to a parent issue.
Teams using gh-sub-issue should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gh-sub-issue/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gh-sub-issue Compares
| Feature / Agent | gh-sub-issue | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
GitHub CLI の extension を使って `gh sub-issue` コマンド経由で Sub Issue を操作する Skill. You can connect existing issues as sub-issues to a parent issue,create new issues directly linked to a parent, unlink sub-issues from their parent without deleting the issues, and view all sub-issues connected to a parent issue.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# gh-sub-issue
## Usage
### Add existing issue as sub-issue
Link an existing issue to a parent issue:
```bash
# Using issue numbers (add existing issue 456 as sub-issue of parent 123)
gh sub-issue add 123 456
# Using URLs (parent issue URL, existing issue number)
gh sub-issue add https://github.com/owner/repo/issues/123 456
# Cross-repository (add existing issue 456 as sub-issue of parent 123)
gh sub-issue add 123 456 --repo owner/repo
```
### Create a new sub-issue
Create a new issue directly linked to a parent:
```bash
# Basic usage
gh sub-issue create --parent 123 --title "Implement user authentication"
# With description and labels
gh sub-issue create --parent 123 \
--title "Add login endpoint" \
--body "Implement POST /api/login endpoint" \
--label "backend,api" \
--assignee "@me"
# With project assignment
gh sub-issue create --parent 123 \
--title "QA Testing Task" \
--project "QA Sprint" \
--assignee "qa-team"
# Multiple projects (GitHub CLI compatible)
gh sub-issue create --parent 123 \
--title "Cross-functional task" \
--project "Dev Sprint" --project "QA Board"
# Using parent issue URL
gh sub-issue create \
--parent https://github.com/owner/repo/issues/123 \
--title "Write API tests"
```
### List sub-issues
View all sub-issues linked to a parent issue:
```bash
# Basic listing
gh sub-issue list 123
# Show all states (open, closed)
gh sub-issue list 123 --state all
# JSON output with selected fields (required)
gh sub-issue list 123 --json number,title,state
# JSON output with parent and meta information
gh sub-issue list 123 --json parent.number,parent.title,total,openCount
# Using URL
gh sub-issue list https://github.com/owner/repo/issues/123
```
### Remove sub-issues
Unlink sub-issues from a parent issue:
```bash
# Remove a single sub-issue
gh sub-issue remove 123 456
# Remove multiple sub-issues
gh sub-issue remove 123 456 457 458
# Skip confirmation prompt
gh sub-issue remove 123 456 --force
# Using URLs
gh sub-issue remove https://github.com/owner/repo/issues/123 456
# Cross-repository
gh sub-issue remove 123 456 --repo owner/repo
```
## 📋 Command Reference
### `gh sub-issue add`
Add an existing issue as a sub-issue to a parent issue.
```plain
Usage:
gh sub-issue add <parent-issue> <sub-issue> [flags]
Arguments:
parent-issue Parent issue number or URL
sub-issue Sub-issue number or URL to be added
Flags:
-R, --repo Repository in OWNER/REPO format
-h, --help Show help for command
```
### `gh sub-issue create`
Create a new sub-issue linked to a parent issue.
```plain
Usage:
gh sub-issue create [flags]
Flags:
-p, --parent Parent issue number or URL (required)
-t, --title Title for the new sub-issue (required)
-b, --body Body text for the sub-issue
-l, --label Comma-separated labels to add
-a, --assignee Comma-separated usernames to assign
-m, --milestone Milestone name or number
--project Projects to add (can specify multiple times)
-R, --repo Repository in OWNER/REPO format
-h, --help Show help for command
```
### `gh sub-issue list`
List all sub-issues for a parent issue.
```plain
Usage:
gh sub-issue list <parent-issue> [flags]
Arguments:
parent-issue Parent issue number or URL
Flags:
-s, --state Filter by state: {open|closed|all} (default: open)
-L, --limit Maximum number of sub-issues to display (default: 30)
--json fields Output JSON with the specified fields
-w, --web Open in web browser
-R, --repo Repository in OWNER/REPO format
-h, --help Show help for command
```
**Field Selection Examples:**
```bash
# All fields (default)
gh sub-issue list 123 --json
# Select specific sub-issue fields
gh sub-issue list 123 --json number,title,state
# Include parent and meta information
gh sub-issue list 123 --json parent.number,parent.title,total,openCount
# Mixed field selection
gh sub-issue list 123 --json number,state,assignees,parent.title
```
### `gh sub-issue remove`
Remove sub-issues from a parent issue.
```plain
Usage:
gh sub-issue remove <parent-issue> <sub-issue> [sub-issue...] [flags]
Arguments:
parent-issue Parent issue number or URL
sub-issue Sub-issue number(s) or URL(s) to remove
Flags:
-f, --force Skip confirmation prompt
-R, --repo Repository in OWNER/REPO format
-h, --help Show help for command
```
## 🎯 Examples
### Real-world workflow
```bash
# 1. Create a parent issue for a feature
gh issue create --title "Feature: User Authentication System" --body "Implement complete auth system"
# Created issue #100
# 2. Create sub-issues for implementation tasks
gh sub-issue create --parent 100 --title "Design database schema" --label "database"
gh sub-issue create --parent 100 --title "Implement JWT tokens" --label "backend"
gh sub-issue create --parent 100 --title "Create login UI" --label "frontend"
# 3. Link an existing issue as a sub-issue
gh sub-issue add 100 95 # Add existing issue #95 as sub-issue
# 4. View progress
gh sub-issue list 100 --state all
# 5. Remove a sub-issue if needed
gh sub-issue remove 100 95 # Unlink issue #95 from parent
```
### Output example
```plain
$ gh sub-issue list 100
Parent: #100 - Feature: User Authentication System
SUB-ISSUES (4 total, 2 open)
─────────────────────────────
✅ #101 Design database schema [closed]
✅ #95 Security audit checklist [closed]
🔵 #102 Implement JWT tokens [open] @alice
🔵 #103 Create login UI [open] @bob
```Related Skills
prepare-issue-pr
Prepare repository-ready Issue or Pull Request drafts using local templates and git/GitHub context. Use this whenever the user wants to create or refine an Issue or PR, especially when they need title/body help, template-aware drafting, related document URLs, or stacked PR base branch guidance for chained branches.
dd-file-issue
File GitHub issues to the right repository (pup CLI or plugin)
typescript-performance
Comprehensive TypeScript performance analysis and optimization. Use when users report slow TypeScript compilation, slow editor experience, or want to investigate TypeScript performance issues. This skill provides diagnostic tools, trace analysis workflows, and optimization strategies. Key triggers include mentions of slow builds, type-checking delays, tsc performance, editor lag with TypeScript, or requests to analyze/improve TypeScript performance. Always prioritize data-driven analysis using --extendedDiagnostics, --generateTrace, and TS Server logs before making optimization recommendations.
watch-ci
CI を監視し、失敗したら自律的に修正してパスするまでループするスキル。push 後・PR 作成後・rebase 後に CI が通るか確認したいとき、CI が落ちていたら直してほしいとき、CI の結果を待ちたいときに使う。「CI 監視して」「CI が通るまで待って」「CI 直して」「push したので CI を見ておいて」など、CI の状態確認・自動修正が必要な場面では必ずこのスキルを呼び出すこと。
vue-style-guide
Vue を書くときは基本的に参考にしてください。 個人的に気に入っている ubgeeei 氏の Vue.js のスタイルガイドです。
vitess
Vitess best practices, query optimization, and connection troubleshooting for PlanetScale Vitess databases. Load when working with Vitess databases, sharding, VSchema configuration, keyspace management, or MySQL scaling issues.
triage-pr-reviews
Triages unresolved PR review comments using gh-pr-reviews. Analyzes code context and classifies each comment as Agree / Partially Agree / Disagree. Walks through each comment one-by-one, asking the user what action to take. Use when the user wants to triage, review, or analyze unresolved PR comments.
terraform-test
Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test syntax and execution.
terraform-style-guide
Generate Terraform HCL code following HashiCorp's official style conventions and best practices. Use when writing, reviewing, or generating Terraform configurations.
terraform-stacks
Comprehensive guide for working with HashiCorp Terraform Stacks. Use when creating, modifying, or validating Terraform Stack configurations (.tfcomponent.hcl, .tfdeploy.hcl files), working with stack components and deployments from local modules, public registry, or private registry sources, managing multi-region or multi-environment infrastructure, or troubleshooting Terraform Stacks syntax and structure.
teach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
stacked-pr
依存関係のある複数の PR を管理・同期するためのスキル。stacked PR のカスケード rebase、PR 間の依存検出、base branch 管理、CI の上流優先修正を行う。PR が別の PR に依存している状況全般で使う — cascade rebase、スタック sync、依存先 PR 更新後のメンテ、PR チェーンの整合性確認などをするときなど。