From github
Closes a GitHub issue with optional comment and close reason (completed, not planned, or duplicate).
How this command is triggered — by the user, by Claude, or both
Slash command
/github:issue-closeThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Close GitHub Issue Close an issue in the claude-power-pack repository. ## Usage The user should provide an issue number. If not provided, ask for it. ## Flow ### Step 1: Verify Issue First, fetch and display the issue to confirm: Show: - Title - Current state - Labels - Brief description ### Step 2: Ask for Closing Comment (Optional) Ask if the user wants to add a closing comment. Common patterns: - "Implemented in [commit/PR]" - "Fixed in v1.x.x" - "Duplicate of #XX" - "Won't fix: [reason]" - "Completed" ### Step 3: Close Reason (Optional) For tracking purposes, ask about th...
Close an issue in the claude-power-pack repository.
The user should provide an issue number. If not provided, ask for it.
First, fetch and display the issue to confirm:
gh issue view NUMBER --repo cooneycw/claude-power-pack
Show:
Ask if the user wants to add a closing comment. Common patterns:
For tracking purposes, ask about the close reason:
# Close as completed (default)
gh issue close NUMBER --repo cooneycw/claude-power-pack
# Close as not planned
gh issue close NUMBER --repo cooneycw/claude-power-pack --reason "not planned"
If closing comment provided, add it first:
gh issue comment NUMBER --repo cooneycw/claude-power-pack --body "COMMENT"
Then close:
gh issue close NUMBER --repo cooneycw/claude-power-pack
After closing, confirm success and show final state.
User: /github:issue-close 42
Claude: [Shows issue #42 details]
This will close issue #42: "Use Plan Mode for complex refactors"
Would you like to add a closing comment? (optional)
User: no
Claude: Close reason?
1. Completed (default)
2. Not Planned
3. Duplicate
User: 1
Claude: Closing issue #42...
Done! Issue #42 has been closed.
User: /github:issue-close 38
Claude: [Shows issue #38 details]
Would you like to add a closing comment?
User: Fixed in commit abc123
Claude: Close reason?
1. Completed (default)
2. Not Planned
3. Duplicate
User: 1
Claude: I'll:
1. Add comment: "Fixed in commit abc123"
2. Close issue #38 as completed
Proceed? (yes/no)
User: yes
Claude: Done! Issue #38 has been closed with your comment.
User: /github:issue-close 45
Claude: [Shows issue details]
Would you like to add a closing comment?
User: Duplicate of #42
Claude: Close reason?
1. Completed
2. Not Planned
3. Duplicate
User: 3
Claude: I'll also add the "duplicate" label for tracking.
[Adds label, adds comment, closes issue]
Done! Issue #45 closed as duplicate of #42.
Mention that issues can be reopened if needed:
gh issue reopen NUMBER --repo cooneycw/claude-power-pack
npx claudepluginhub cooneycw/claude-power-pack --plugin github/issue-closeCloses a GitHub or Gitea issue with comprehensive summary of work completed, verification checklist, related commits/PRs, artifacts, and next steps. Supports custom reason, no-verify, and link-artifacts flags.
/close-issueCreates a Pull Request that auto-closes the specified GitHub issue when merged, using isolated git worktrees. Supports --dry-run, --json, --no-worktree, --skip-retro flags.
/closeCloses a completed beads issue by ID with optional reason. Prompts for ID if missing, confirms with details via MCP close tool, and suggests checking dependents or new work.
/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.
/github-issue-fixAnalyzes GitHub issue via gh CLI, identifies sub-issues/dependencies, breaks into tasks, and documents structured fix plan in scratchpad.