How do I install the Sub Issue skill?

Run npx skillmds@latest add posit-dev/sub-issue in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sub Issue safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sub Issue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sub Issue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sub Issue?

posit-dev (@posit-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sub Issue by posit-dev — Agent Skill

Name: Sub Issue
Author: posit-dev

File contents

GitHub Sub-Issue Management

Manage GitHub sub-issues (child issues) using native gh CLI commands (v2.94.0+).

Prerequisites

Before using any sub-issue commands, verify the gh CLI is v2.94.0 or newer:

gh --version

If the version is older than 2.94.0, the native sub-issue flags (--parent, --add-sub-issue, --remove-sub-issue, --remove-parent) will not be available. In that case, advise the user to upgrade gh before proceeding.

Commands

Create a new sub-issue

Create a new issue directly linked as a child of a parent issue:

gh issue create --parent <parent-issue> --title "<title>" --body "<body>" --repo posit-dev/py-shiny

Flags:

--parent — Parent issue number or URL (required for sub-issue linking)
--title — Title for new sub-issue (required)
--body — Body text for the sub-issue
--label — Comma-separated labels
--assignee — Comma-separated usernames
--milestone — Milestone name or number
--project — Project to add the issue to

Add an existing issue as a sub-issue

gh issue edit <parent-issue> --add-sub-issue <child-issue> --repo posit-dev/py-shiny

Set or change the parent of an issue

gh issue edit <child-issue> --parent <parent-issue> --repo posit-dev/py-shiny

List sub-issues of a parent

gh issue view <parent-issue> --json subIssues,subIssuesSummary --repo posit-dev/py-shiny

Remove a sub-issue link

gh issue edit <parent-issue> --remove-sub-issue <child-issue> --repo posit-dev/py-shiny

Remove parent from an issue

gh issue edit <child-issue> --remove-parent --repo posit-dev/py-shiny

Usage Notes

Always include --repo posit-dev/py-shiny to ensure correct repository context
When creating multiple sub-issues, create them sequentially to avoid rate limiting
Use --body with heredoc for multi-line descriptions:

gh issue create --parent 123 --title "My issue" --body "$(cat <<'EOF'
Description here.

**Acceptance criteria:**
1. First item
2. Second item
EOF
)" --repo posit-dev/py-shiny

Reference the parent issue in the body for context (e.g., "Part of #123")

---name: sub-issuedescription: Manage GitHub sub-issues using the gh CLI (v2.94.0+). Use when the user asks to create, list, add, or remove sub-issues (child issues) from a parent issue.---# GitHub Sub-Issue ManagementManage GitHub sub-issues (child issues) using native `gh` CLI commands (v2.94.0+).## PrerequisitesBefore using any sub-issue commands, verify the `gh` CLI is v2.94.0 or newer:```bashgh --version```If the version is older than 2.94.0, the native sub-issue flags (`--parent`, `--add-sub-issue`, `--remove-sub-issue`, `--remove-parent`) will not be available. In that case, advise the user to upgrade `gh` before proceeding.## Commands### Create a new sub-issueCreate a new issue directly linked as a child of a parent issue:```bashgh issue create --parent <parent-issue> --title "<title>" --body "<body>" --repo posit-dev/py-shiny```**Flags:**- `--parent` — Parent issue number or URL (required for sub-issue linking)- `--title` — Title for new sub-issue (required)- `--body` — Body text for the sub-issue- `--label` — Comma-separated labels- `--assignee` — Comma-separated usernames- `--milestone` — Milestone name or number- `--project` — Project to add the issue to### Add an existing issue as a sub-issue```bashgh issue edit <parent-issue> --add-sub-issue <child-issue> --repo posit-dev/py-shiny```### Set or change the parent of an issue```bashgh issue edit <child-issue> --parent <parent-issue> --repo posit-dev/py-shiny```### List sub-issues of a parent```bashgh issue view <parent-issue> --json subIssues,subIssuesSummary --repo posit-dev/py-shiny```### Remove a sub-issue link```bashgh issue edit <parent-issue> --remove-sub-issue <child-issue> --repo posit-dev/py-shiny```### Remove parent from an issue```bashgh issue edit <child-issue> --remove-parent --repo posit-dev/py-shiny```## Usage Notes1. Always include `--repo posit-dev/py-shiny` to ensure correct repository context2. When creating multiple sub-issues, create them sequentially to avoid rate limiting3. Use `--body` with heredoc for multi-line descriptions:```bashgh issue create --parent 123 --title "My issue" --body "$(cat <<'EOF'Description here.**Acceptance criteria:**1. First item2. Second itemEOF)" --repo posit-dev/py-shiny```4. Reference the parent issue in the body for context (e.g., "Part of #123")

Frequently asked questions

Sub Issue