close-workflow

Automate pull request closing, deployment verification, branch merging, and cleanup.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/cursor-js/cursor.js --skill close-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: close-workflow
Source: https://github.com/cursor-js/cursor.js/tree/main/.agents/skills/close-workflow
Command: npx skills add https://github.com/cursor-js/cursor.js --skill close-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex process of closing pull requests, verifying deployments, merging branches, and cleaning up local and remote branches, reducing manual effort and errors.

Core Features & Use Cases

  • PR and Deployment Verification: Checks pull request status, review checks, and deployment success or failure, including polling Vercel preview URLs.
  • Approval and Merge Automation: Prompts for user approval before merging PRs using specified strategies, ensuring controlled deployments.
  • Branch Cleanup: Automates switching to base branches, deleting feature branches both locally and remotely, and pruning the origin, maintaining repository hygiene.
  • Use Case: A developer finishes a feature branch, wants to quickly verify deployment, merge after approval, and clean up all related branches with minimal manual commands.

Quick Start

Use this skill to verify your current PR, approve deployment, merge into main, and delete branch histories seamlessly.

Frequently Asked Questions about close-workflow

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

FAQPage Schema
How do I automate closing a pull request and cleaning up git branches after merging?

To automate closing a pull request and cleaning up git branches, this skill verifies PR checks and deployment statuses, prompts for approval, merges the branch, and deletes local and remote feature branches automatically.

Can I verify Vercel preview deployments before merging a pull request?

Yes, you can verify Vercel preview deployments before merging a pull request. The skill polls preview URLs to check deployment success or failure, ensuring controlled deployments prior to branch merging.

What is the best way to automate repository branch cleanup after feature completion?

The best way to automate repository branch cleanup is using a workflow that switches to the base branch, deletes feature branches locally and remotely, and prunes the origin to maintain repository hygiene efficiently.

Does this PR closure workflow require manual approval before merging branches?

Yes, this PR closure workflow requires manual approval before merging branches. It prompts the user to approve deployment using specified merge strategies, ensuring safe and controlled repository maintenance.

Why should I automate branch deletion and origin pruning in git?

You should automate branch deletion and origin pruning in git to reduce manual effort and errors. Automating these commands maintains repository hygiene seamlessly after feature completion and deployment verification.

Are there limitations when automating git branch cleanup and PR merging?

A limitation of automating git branch cleanup and PR merging is the dependency on scripting and branch management commands. Users must ensure correct git interactions and deployment statuses are met before safe execution.