b9-close

Close GitHub pull requests and resolve linked issues and worktrees.

6|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/jporre/sveltekit-verticalslices --skill b9-close
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b9-close
Source: https://github.com/jporre/sveltekit-verticalslices/tree/main/skills/b9-close
Command: npx skills add https://github.com/jporre/sveltekit-verticalslices --skill b9-close

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-api, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of closing pull requests, resolving associated issues, and cleaning up worktrees, ensuring project integrity and efficiency.

Core Features & Use Cases

  • Automated PR Closing: Closes pull requests with approval, merges them into the default branch, and cleans up the worktree.
  • Issue Resolution: Ensures all associated issues are closed when a PR is merged.
  • Worktree Cleanup: Removes the worktree and its branches, maintaining a clean project environment.
  • Use Case: When a pull request is approved and ready to be merged, this Skill can be used to automatically close the PR, resolve the issues, and clean up the worktree, saving time and reducing manual effort.

Quick Start

Close the pull request #123 with the command: close-pr #123

Frequently Asked Questions about b9-close

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically close a GitHub pull request and clean up the worktree?

To automatically close a GitHub pull request and clean up the worktree, you can use a tool that merges the PR into the default branch and removes the associated worktree. This ensures project integrity by automating branch management upon PR approval.

How does issue resolution work when merging a pull request?

Issue resolution during a pull request merge works by automatically closing all associated issues in GitHub once the PR is merged. This ensures that issue tracking remains synchronized with code changes without requiring manual updates.

Do I need GitHub API access to automate pull request closing?

Yes, you need GitHub API access and appropriate permissions to automate pull request closing. Accessing the GitHub API is required for managing PRs, resolving issues, and executing Git commands for branch management.

Can I use Git commands to manage branches when closing a pull request?

Yes, you can use Git commands to manage branches when closing a pull request. The automation utilizes Git for worktree management and branch cleanup, ensuring the local project environment is maintained after merging.

What is the best way to maintain project integrity during PR cleanup?

The best way to maintain project integrity during PR cleanup is to automate the entire process: merge the approved PR, resolve linked issues, and remove the worktree branches. This reduces manual effort and prevents stale branches.

Why should I clean up worktrees after merging a pull request?

You should clean up worktrees after merging a pull request to maintain a clean project environment. Removing the worktree and its branches prevents clutter and ensures that stale code does not interfere with future development.