From gaac
Updates issues related to a merged PR by finding or accepting a PR number and running a script to close, notify, and cascade-update linked issues.
How this command is triggered — by the user, by Claude, or both
Slash command
/gaac:update-related-issues <issue-or-pr-number>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /update-related-issues Update related issues after a PR has been merged. This is a convenience wrapper that accepts either a PR number or an issue number. ## Context - Repository: !`gh repo view --json nameWithOwner -q '.nameWithOwner'` - Argument: $1 ## Usage **Note**: Input must be a numeric PR or issue number (no leading #). --- ## Phase 1: Determine Type First, check if the argument is a PR or an issue: ### 1.1 Check if PR Exists If this succeeds, the argument is a PR number - proceed to Phase 2. ### 1.2 If Not a PR, Treat as Issue If the PR check fails, the argument i...
Update related issues after a PR has been merged. This is a convenience wrapper that accepts either a PR number or an issue number.
gh repo view --json nameWithOwner -q '.nameWithOwner'/update-related-issues 123 # PR number
/update-related-issues 42 # Issue number (finds associated PR)
Note: Input must be a numeric PR or issue number (no leading #).
First, check if the argument is a PR or an issue:
gh pr view $1 --json number,state,mergedAt 2>/dev/null
If this succeeds, the argument is a PR number - proceed to Phase 2.
If the PR check fails, the argument is likely an issue number.
Try to find a merged PR that resolves this issue:
# Search for merged PRs that resolve this issue
gh pr list --state merged --search "resolves #$1" --json number,title --limit 5
# Also try alternative patterns
gh pr list --state merged --search "fixes #$1" --json number,title --limit 5
gh pr list --state merged --search "closes #$1" --json number,title --limit 5
If a merged PR is found, use that PR number. If multiple are found, use the most recent.
If no merged PR is found, inform the user:
No merged PR found that resolves issue #$1.
To update related issues, please provide the PR number directly:
/update-related-issues <pr-number>
Or merge a PR that includes "Resolves #$1" in its description first.
Once a valid merged PR number is determined, call the update script:
bash "${CLAUDE_PLUGIN_ROOT}/skills/github-manager/scripts/update-related-issues.sh" \
--pr <pr-number>
Report the actions taken:
| Action | Count |
|---|---|
| Issues closed | N |
| Related issues notified | N |
| Dependent issues notified | N |
| Cascade closures | N |
If there were errors or warnings, list them for the user to review.
npx claudepluginhub sihaoliu/gaac --plugin gaac/issue-linkageAnalyzes current PR against open repo issues for coverage, comments on fully/partially addressed status, and closes resolved ones via GitHub CLI.
/close-issueAnalyzes GitHub/GitLab issues to determine if they can be closed based on commits and codebase changes. Reports completion status, gaps with tasks, and offers fixes.
/issue-syncDetects issue references (Fixes #123, etc.) in git commits, artifacts, and code, then updates GitHub/gh or Gitea issues (close, progress/blocker comments). Supports --commit, --scan-recent, --artifact, --dry-run.
/pickup-githubExecutes GitHub workflows for picking up board issues: fetches open issues, detects collisions, updates status labels, creates PRs with issue linkage, and transitions labels to in-review.
/fixprcAutonomously fixes PR comments, review feedback, merge-blocking issues, and CI problems using iterative genesis and copilot until PR is mergeable (max 7 iterations).