Menu
Add a dependency relationship between GitHub issues using the native addBlockedBy mutation
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Reusable file sequence numbering with prefix (NNNN-name) and suffix (name-NNNN) modes. Returns the next available zero-padded sequence number for a given directory.
Drop a timestamped note for the current issue - collected by /finish-issue for PR descriptions
Create or update CHANGELOG entries with tone guardrails, thematic grouping, and implementation-detail leak detection.
Delete an issue's working directory (.claude-work/issues/<ID>/) after confirming with the user via interactive prompt
Create a commit message file in .claude-work/commit-msgs/ with auto-numbered filenames. Focuses on WHY not WHAT. The diff already shows what changed. User reviews and commits manually.
Create a GitHub issue from a file draft or inline description, with smart label discovery and sub-issue linking
| name | add-github-dependency |
| version | 2026.07.27@6dc7d1d |
| description | Add a dependency relationship between GitHub issues using the native addBlockedBy mutation |
| argument-hint | <blocked-by|is-blocking> <issue-url> |
| user-invocable | true |
| allowed-tools | Read, Bash(*/skills/create-github-issue/link-dependency.sh *), Bash(*/skills/issue-context/target-path.sh *), Bash(*/skills/issue-context/claude-work-root.sh *), Bash(gh repo view *) |
Add a dependency relationship between GitHub issues using GitHub's native addBlockedBy mutation. Works cross-repo — node IDs are globally unique, so the mutation handles same-repo and cross-repo identically.
Input: $ARGUMENTS — a relationship type (blocked-by or is-blocking) followed by a target issue URL.
Split $ARGUMENTS on whitespace. The first token is the relationship type; the second is the target issue URL.
Validate the relationship type:
blocked-by — the current issue IS BLOCKED BY the target issue
is-blocking — the current issue IS BLOCKING the target issue
If the relationship type is not one of these two values, print an error and exit:
add-github-dependency: invalid relationship type '<type>'. Expected 'blocked-by' or 'is-blocking'.
Usage: /add-github-dependency <blocked-by|is-blocking> <issue-url>
Parse the target URL to extract owner, repo, and issue number. The URL format is:
https://github.com/<owner>/<repo>/issues/<number>
If the URL does not match this pattern, print an error and exit:
add-github-dependency: could not parse issue URL '<url>'. Expected format: https://github.com/<owner>/<repo>/issues/<number>
Resolve the current branch's issue number as the subject via target-path.sh:
~/.claude/skills/issue-context/target-path.sh
Parse the subject issue number from the branch name (e.g., issues/182 → 182). If the current branch is not an issues/* branch, print an error and exit:
add-github-dependency: current branch is not an issues/* branch. Switch to the issue branch for the subject issue first.
Determine the subject's owner and repo from the current git remote:
gh repo view --json owner,name
If this fails, print an error and exit:
add-github-dependency: could not determine current repository. Run from within a git repository.
Call the unified linking script:
~/.claude/skills/create-github-issue/link-dependency.sh \
--subject-owner "$SUBJECT_OWNER" \
--subject-repo "$SUBJECT_REPO" \
--subject-number "$SUBJECT_NUMBER" \
--target-owner "$TARGET_OWNER" \
--target-repo "$TARGET_REPO" \
--target-number "$TARGET_NUMBER" \
--relationship "$RELATIONSHIP"
Report the result:
On success: print the script's output line.
On failure: print the error and exit with:
add-github-dependency: linking failed — <error message>
Formatting: see /prose-style for hard-wrap, code-reference, and GitHub-reference rules.