skills.rest
VIPER-Metrics
VIPER-MetricsOFFICIAL
Explore all skills by this author →
GitHub

close-pr

Close pull requests after testing and finalize issues, wiki docs, and worktrees.

1|Updated Jan 19, 2026
Search Tags:#code-review#pull-request#issue-management#gh-cli#pr-automation#close-pr
One-click install
npx skills add https://github.com/VIPER-Metrics/claude-code-skills --skill close-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: close-pr
Source: https://github.com/VIPER-Metrics/claude-code-skills/tree/main/skills/close-pr
Command: npx skills add https://github.com/VIPER-Metrics/claude-code-skills --skill close-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates closing a completed pull request after testing confirms the fix, including PR merging when appropriate, finalizing the associated issue, archiving related wiki documentation, and cleaning up worktrees.

Core Features & Use Cases

  • PR validation and closure: Determine PR status (merged or open), verify testing has completed, and close the issue accordingly.
  • Automation of finalization steps: Merge the PR if required, post a closing comment, update labels, and archive wiki docs.
  • Cleanup and notification: Remove temporary worktrees and notify the issue owner to keep stakeholders informed.

Quick Start

Run /close-pr {issue_number} after you have completed testing in staging and are ready to finalize the work.

Frequently Asked Questions about close-pr

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

FAQPage Schema
How do I automatically close a pull request after testing is complete?▼

Automating pull request closure after testing validates PR status, applies optional merge actions, posts closing comments, and updates labels. You trigger this finalization process by running the command with the associated issue number.

What steps are needed to finalize an open PR and its associated issue?▼

Finalizing an open PR and its associated issue involves validating the PR status, merging the code if required, posting a closing comment, updating labels, and archiving related wiki documentation to complete the development cycle.

Does PR closure automation handle worktree cleanup and wiki archival?▼

Yes, PR closure automation handles both local worktree cleanup and wiki archival. It removes temporary worktrees and archives related wiki documents as part of the finalization steps after testing confirms the fix.

Can I merge a pull request and close the linked issue at the same time?▼

You can merge a pull request and close the linked issue simultaneously using PR finalization automation. It verifies testing completion, applies the required merge, updates issue labels, and notifies the issue owner in one action.

When should I use an automated PR closing workflow instead of manual closure?▼

You should use an automated PR closing workflow when you need to consistently validate PR status, merge code, update labels, archive wiki docs, and clean up worktrees across multiple development scenarios without manual intervention.

Related Skills

Explore More Software Engineering Skills→
Nairon-AINairon-AI
7

flux-gate

Validate staging deployments and generate promotion pull requests.

Official
Advanced
N0K0N0K0

finish-issue

Automate GitHub issue closure with test verification, PR creation, and umbrella tracking.

Community
Advanced
makoMakoGomakoMakoGo
7

github-issue-pr-flow

Automate GitHub issue-to-pull-request workflows with branch management and squash-merging.

Community
Advanced
AncienttwoAncienttwo
407

repo-harness-ship

Finalize worktrees and create GitHub pull requests with review gates.

Community
Intermediate