issue-management
starsforks
How to install issue-management?
remotion-dev/remotion/issue-management
$npx -y skills add remotion-dev/remotion --skill issue-managementManage GitHub Issues 2.0 relationships with gh CLI: parent issues, sub-issues, blocked-by, and blocking links.
SKILL.md
| 1 | Use this skill when creating, editing, inspecting, or removing relationships between GitHub issues. |
| 2 | |
| 3 | These commands use the Issues 2.0 `gh issue` support added in GitHub CLI PR [cli/cli#13057](https://github.com/cli/cli/pull/13057). Because this feature is new, first confirm the installed `gh` supports it: |
| 4 | |
| 5 | ```bash |
| 6 | gh issue create --help | grep -E -- '--parent|--blocked-by|--blocking' |
| 7 | gh issue edit --help | grep -E -- '--parent|--add-sub-issue|--add-blocked-by|--add-blocking' |
| 8 | ``` |
| 9 | |
| 10 | If those flags are missing, update `gh` before trying to manage issue relationships. Do not invent older commands. |
| 11 | |
| 12 | ## Issue reference format |
| 13 | |
| 14 | Relationship flags accept issue numbers or issue URLs. |
| 15 | |
| 16 | Use a number for an issue in the current repository: |
| 17 | |
| 18 | ```bash |
| 19 | gh issue edit 123 --parent 100 |
| 20 | ``` |
| 21 | |
| 22 | Use a full issue URL for a cross-repository relationship: |
| 23 | |
| 24 | ```bash |
| 25 | gh issue edit 123 --blocked-by https://github.com/remotion-dev/remotion/issues/456 |
| 26 | ``` |
| 27 | |
| 28 | Multiple related issues can be passed as a comma-separated list: |
| 29 | |
| 30 | ```bash |
| 31 | gh issue edit 123 --add-blocked-by 200,201 |
| 32 | ``` |
| 33 | |
| 34 | ## Parent and sub-issue relationships |
| 35 | |
| 36 | A sub-issue has exactly one parent issue. |
| 37 | |
| 38 | To create a new issue directly under a parent: |
| 39 | |
| 40 | ```bash |
| 41 | gh issue create \ |
| 42 | --title 'Docs: Add issue management skill' \ |
| 43 | --body-file /tmp/remotion-issue-body.md \ |
| 44 | --parent 100 |
| 45 | ``` |
| 46 | |
| 47 | To set or change the parent of an existing child issue: |
| 48 | |
| 49 | ```bash |
| 50 | gh issue edit <child-number> --parent <parent-number-or-url> |
| 51 | ``` |
| 52 | |
| 53 | To remove the parent from a child issue: |
| 54 | |
| 55 | ```bash |
| 56 | gh issue edit <child-number> --remove-parent |
| 57 | ``` |
| 58 | |
| 59 | To manage children from the parent issue: |
| 60 | |
| 61 | ```bash |
| 62 | gh issue edit <parent-number> --add-sub-issue <child-number-or-url> |
| 63 | gh issue edit <parent-number> --remove-sub-issue <child-number-or-url> |
| 64 | ``` |
| 65 | |
| 66 | `--add-sub-issue` moves the child to the new parent if it already has another parent. Do not use `--add-sub-issue` while editing multiple parent issues in one command; one child cannot be added ambiguously to several parents. |
| 67 | |
| 68 | ## Blocked-by and blocking relationships |
| 69 | |
| 70 | Use `blocked-by` when the issue being edited is waiting on another issue. |
| 71 | |
| 72 | ```bash |
| 73 | # Issue 123 is blocked by issue 200. |
| 74 | gh issue edit 123 --add-blocked-by 200 |
| 75 | |
| 76 | # Remove that relationship. |
| 77 | gh issue edit 123 --remove-blocked-by 200 |
| 78 | ``` |
| 79 | |
| 80 | Use `blocking` when the issue being edited blocks another issue. |
| 81 | |
| 82 | ```bash |
| 83 | # Issue 123 is blocking issues 300 and 301. |
| 84 | gh issue edit 123 --add-blocking 300,301 |
| 85 | |
| 86 | # Remove one blocking relationship. |
| 87 | gh issue edit 123 --remove-blocking 300 |
| 88 | ``` |
| 89 | |
| 90 | Equivalent mental model: |
| 91 | |
| 92 | ```bash |
| 93 | gh issue edit A --add-blocking B |
| 94 | ``` |
| 95 | |
| 96 | means the same relationship as: |
| 97 | |
| 98 | ```bash |
| 99 | gh issue edit B --add-blocked-by A |
| 100 | ``` |
| 101 | |
| 102 | Choose the command based on which issue you are already editing. |
| 103 | |
| 104 | When creating an issue, set relationships immediately: |
| 105 | |
| 106 | ```bash |
| 107 | gh issue create \ |
| 108 | --title 'Studio: Add timeline validation' \ |
| 109 | --body-file /tmp/remotion-issue-body.md \ |
| 110 | --blocked-by 200,201 \ |
| 111 | --blocking 300 |
| 112 | ``` |
| 113 | |
| 114 | ## Inspecting relationships |
| 115 | |
| 116 | Human-readable view shows parent, sub-issues, blocked-by, and blocking metadata when present: |
| 117 | |
| 118 | ```bash |
| 119 | gh issue view <number> |
| 120 | ``` |
| 121 | |
| 122 | Raw non-TTY output includes stable relationship lines: |
| 123 | |
| 124 | ```bash |
| 125 | gh issue view <number> | grep -E '^(parent|sub-issues|sub-issues-completed|blocked-by|blocking):' |
| 126 | ``` |
| 127 | |
| 128 | For scripts, request the JSON fields explicitly: |
| 129 | |
| 130 | ```bash |
| 131 | gh issue view <number> \ |
| 132 | --json parent,subIssues,subIssuesSummary,blockedBy,blocking |
| 133 | ``` |
| 134 | |
| 135 | `subIssues`, `blockedBy`, and `blocking` are connection objects with `nodes` and `totalCount`. `subIssuesSummary` contains completion counts. |
| 136 | |
| 137 | ## Safe workflow |
| 138 | |
| 139 | 1. Create any new issue bodies with `--body-file`, not inline multiline shell strings. |
| 140 | 2. Link the relationship using the appropriate `gh issue create` or `gh issue edit` flag. |
| 141 | 3. Verify with `gh issue view <number>` or `gh issue view <number> --json parent,subIssues,subIssuesSummary,blockedBy,blocking`. |
| 142 | 4. If editing a PR or parent issue body afterward, replace vague checklist text with concrete issue numbers. |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
