finish-issue

Automate GitHub issue completion with commits, pull requests, and cleanup.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aifuun/u-safe --skill finish-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-issue
Source: https://github.com/aifuun/u-safe/tree/main/.claude/skills/finish-issue
Command: npx skills add https://github.com/aifuun/u-safe --skill finish-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire process of finishing a GitHub issue, from committing code to closing the issue, saving significant time and reducing manual errors.

Core Features & Use Cases

  • Automated Git Workflow: Commits changes, creates pull requests, and merges them.
  • Issue Lifecycle Management: Automatically closes the GitHub issue upon successful merge.
  • Cleanup: Removes local branches and cleans up temporary files.
  • Use Case: After implementing a new feature for issue #123, you can simply say "finish issue #123" and the Skill will handle all the necessary Git commands, PR creation, merging, and issue closing.

Quick Start

Use the finish-issue skill to complete issue number 123.

Frequently Asked Questions about finish-issue

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

FAQPage Schema
How do I automate closing a GitHub issue after merging a pull request?

Automating GitHub issue closure after a pull request merge is handled by validating code, committing with semantic messages, merging the PR, and automatically closing the linked issue. This removes manual errors.

What is the best way to automate a git workflow from code commit to issue closure?

Automating the git workflow involves pre-finish validation, committing code, creating and merging pull requests, closing the GitHub issue, and cleaning up branches and temporary files in one seamless end-to-end process.

Can I keep my local branches after merging a pull request?

Yes, you can keep local branches after merging. This issue workflow supports various scenarios like keeping branches, skipping merges, and performing dry runs while integrating with code review status.

Does this automated GitHub issue workflow support dry runs?

Yes, dry runs are supported. The workflow handles scenarios like skipping merges and dry runs, allowing you to validate the end-to-end issue completion process without permanently altering branches or closing issues.

How do I run a pre-finish validation before creating a pull request?

Pre-finish validation runs automatically before creating a pull request. It checks code review status and issue detection mechanisms to ensure requirements are met before committing code and merging the pull request.