Skill522 repo starsupdated today

close-issue

The close-issue Claude Code skill closes GitHub or GitLab issues by first detecting the version control provider from repository context, extracting issue details including title and comments, generating a contextual summary comment that references related pull requests or commits, and then posting the comment before closing the issue with either a "completed" or "not_planned" reason. Use this skill when you need to programmatically resolve issues across different Git platforms with appropriate documentation of the resolution.

View source Repository: agent-swarm

Install in Claude Code

Copy

git clone --depth 1 https://github.com/desplega-ai/agent-swarm /tmp/close-issue && cp -r /tmp/close-issue/plugin/pi-skills/close-issue ~/.claude/skills/close-issue

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# Close Issue

Close a GitHub or GitLab issue with an appropriate closing comment summarizing the resolution.

**Provider detection:** Check the URL or remote to determine the VCS provider:
- If GitHub → use `gh issue close` / `gh issue comment`
- If GitLab → use `glab issue close` / `glab issue note`

## Arguments

- `issue-number-or-url`: Either an issue number (e.g., `123`) or a full issue URL

## Workflow

1. **Parse the input** — if given a URL, extract owner, repo, and issue number. If just a number, use the current repo context.
2. **Ensure repo is cloned** to `/workspace/personal/<repo-name>` (clone with `gh repo clone` if needed).
3. **Get issue details** — read the issue title, body, comments, and check for related PRs.
4. **Generate closing comment** — summarize what was done, reference related PRs/commits, note any follow-ups.
5. **Post comment and close:**
   ```bash
   gh issue close <issue-number> --comment "Your closing comment" --reason completed
   ```

## Closing Reasons

- `completed` — The issue was resolved
- `not_planned` — Won't fix / out of scope / duplicate

## Tips

- Always explain why the issue is being closed
- Reference specific PRs or commits when applicable
- If closing as "not planned", explain the reasoning