manage-github-issue-dependencies

You can automate GitHub issue dependencies by using Ruby scripts that call the GitHub REST API via the gh CLI. This skill creates, deletes, and lists blocked_by and blocking relationships between issues to streamline project management workflows across repositories.

To list blocking GitHub issues, run a Ruby script targeting a specific repository and issue number. The script queries the GitHub REST API to retrieve the current dependency graph, showing which issues block or are blocked by the given issue for quick context.

Yes, managing issue dependencies with this skill requires the GitHub CLI (gh) and Ruby to execute the underlying scripts. You also need network access and appropriate repository permissions to call the GitHub REST API for creating and removing dependency relationships.

Removing a blocking relationship is done by executing a Ruby script that calls the GitHub REST API to detach an existing dependency. You provide the owner, repository, and the two issue numbers to remove the specific blocked_by or blocking link between them.

Tracking blocked_by and blocking relationships improves GitHub project coordination by explicitly mapping prerequisites and work order. Teams can quickly view dependency graphs to understand which issues must be resolved before others can proceed, reducing planning friction across repositories.

Cross-repository dependency updates fail when network access is unavailable or repository permissions are insufficient. The Ruby scripts rely on the gh CLI to authenticate and call the GitHub REST API, so ensure your token has the correct scopes for all target repositories.