How do I install the Ghp:wrap Issue skill?

Run npx skillmds@latest add fredericosantos/ghp-wrap-issue in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ghp:wrap Issue safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ghp:wrap Issue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ghp:wrap Issue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ghp:wrap Issue?

fredericosantos (@fredericosantos) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ghp:wrap Issue by fredericosantos — Agent Skill

Name: Ghp:wrap Issue
Author: fredericosantos

File contents

/ghp:wrap-issue — Close Out an Issue

Flow

Identify the issue. If not specified, infer from the current branch name. The branch naming convention encodes the issue number:
- Milestone issue: m7/42-batch-tree-eval → issue #42
- Sub-issue: m7/42/43-fitness-function → issue #43
- Standalone: 7-duplicate-fitness → issue #7
Check sub-issues. Run gh issue-ext sub list <issue> to find sub-issues. Verify all are closed or ready to close. If any are still open, ask the user whether to close them or stop.
Check blockers. Run gh issue-ext blocking list <issue> to confirm no unresolved blockers remain.
Determine the target branch from the current branch name:
- Sub-issue branch m7/42/43-... → PR targets the parent issue branch m7/42-...
- Issue branch m7/42-... → PR targets the milestone branch m7-{name}
- Standalone branch → PR targets main
Set issue status to Review in the Project using gh pm move <issue> --status review (signals "work complete, PR open for review"). The built-in "Item closed" workflow auto-moves to Done when the PR merges and closes the issue.

Create the PR. The PR body must include closes #<issue> and closes #<sub-issue> for every completed sub-issue:

gh pr create --base m7-new-eval-strategy \
  --title "feat(eval): batch tree evaluation #42" \
  --body "## Summary
<what changed>

closes #42
closes #43
closes #44"

Write a summary comment on the issue:

gh issue comment 42 --body "## Summary
<brief description of what was done, key changes>

PR: #N"

Clean up branches. After the PR is created, ask the user via AskUserQuestion what to do with the branch:

Option Action

Keep Leave the branch as-is

Delete local only git branch -d <branch>

Delete remote only git push origin --delete <branch>

Delete both Delete local and remote

If there are sub-issue branches that were merged into this branch, ask about each one separately. Switch to the target branch before deleting:
```
git checkout <target-branch>
```
Notify the user with the PR URL and a summary of what was closed.

Option	Action
Keep	Leave the branch as-is
Delete local only	`git branch -d <branch>`
Delete remote only	`git push origin --delete <branch>`
Delete both	Delete local and remote

---name: ghp-wrap-issuedescription: Close out an issue. Writes a summary comment, creates a PR to the milestone branch (or main for standalone issues), and closes all completed sub-issues.---# /ghp:wrap-issue — Close Out an Issue## Flow1. **Identify the issue.** If not specified, infer from the current branch name. The branch naming convention encodes the issue number: - Milestone issue: `m7/42-batch-tree-eval` → issue #42 - Sub-issue: `m7/42/43-fitness-function` → issue #43 - Standalone: `7-duplicate-fitness` → issue #72. **Check sub-issues.** Run `gh issue-ext sub list <issue>` to find sub-issues. Verify all are closed or ready to close. If any are still open, ask the user whether to close them or stop.3. **Check blockers.** Run `gh issue-ext blocking list <issue>` to confirm no unresolved blockers remain.4. **Determine the target branch** from the current branch name: - Sub-issue branch `m7/42/43-...` → PR targets the parent issue branch `m7/42-...` - Issue branch `m7/42-...` → PR targets the milestone branch `m7-{name}` - Standalone branch → PR targets main5. **Set issue status to Review** in the Project using `gh pm move <issue> --status review` (signals "work complete, PR open for review"). The built-in "Item closed" workflow auto-moves to Done when the PR merges and closes the issue.6. **Create the PR.** The PR body must include `closes #<issue>` and `closes #<sub-issue>` for every completed sub-issue: ```bash gh pr create --base m7-new-eval-strategy \ --title "feat(eval): batch tree evaluation #42" \ --body "## Summary <what changed> closes #42 closes #43 closes #44" ```7. **Write a summary comment** on the issue: ```bash gh issue comment 42 --body "## Summary <brief description of what was done, key changes> PR: #N" ```8. **Clean up branches.** After the PR is created, ask the user via `AskUserQuestion` what to do with the branch: | Option | Action | |---|---| | Keep | Leave the branch as-is | | Delete local only | `git branch -d <branch>` | | Delete remote only | `git push origin --delete <branch>` | | Delete both | Delete local and remote | If there are sub-issue branches that were merged into this branch, ask about each one separately. Switch to the target branch before deleting: ```bash git checkout <target-branch> ```9. **Notify the user** with the PR URL and a summary of what was closed.

Frequently asked questions

Ghp:wrap Issue