skills.rest
N0K0
N0K0COMMUNITY
Explore all skills by this author →
WebsiteGitHub

finish-issue

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

Updated Mar 28, 2026
Search Tags:#github#worktree-management#dev-workflow#pr-creation#test-verification#issue-closure#umbrella-tasks
One-click install
npx skills add https://github.com/N0K0/claude-plugins-backalley --skill finish-issue-n0k0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finish-issue
Source: https://github.com/N0K0/claude-plugins-backalley/tree/main/plugins/process/skills/finish-issue
Command: npx skills add https://github.com/N0K0/claude-plugins-backalley --skill finish-issue-n0k0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually wrapping up completed GitHub issues is error-prone and time-consuming, requiring repeated checks for passing tests, proper PR creation with closure tags, parent issue tracking, and worktree cleanup that are easy to skip or mess up.

Core Features & Use Cases

  • Pre-closure validation: Automatically checks for the in-progress label, fully completed implementation checklists, and passing test suites before allowing any closure work to proceed.
  • Flexible merge paths: Supports three merge options: PR merge with automatic GitHub issue closure, leaving the PR open for external review, or local merge with manual state syncing to GitHub.
  • Umbrella issue tracking: Automatically checks off parent umbrella issues when all child tasks are complete, with recursive checking up to 5 levels to avoid cycles.
  • Use Case: For development teams using GitHub Issues to track work, this skill eliminates manual overhead and mistakes when closing out completed features, bug fixes, or tasks.

Quick Start

Use the finish-issue skill to wrap up all closure steps for completed GitHub issue #42, including test verification, PR creation, and parent issue checkoff.

Frequently Asked Questions about finish-issue

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

FAQPage Schema
How do I automate GitHub issue closure and PR creation?▼

Automate GitHub issue closure by validating completed implementation checklists and passing test suites, then create PRs with auto-closure tags. This eliminates manual validation and PR creation overhead for development workflows.

How does umbrella issue tracking work when closing child tasks?▼

Umbrella issue tracking automatically checks off parent issues when all child tasks are complete, recursively checking up to 5 levels to avoid cycles. This ensures parent GitHub issues are accurately updated without manual intervention.

What are the merge options for closing GitHub issues with test verification?▼

Test verification supports three merge options: PR merge with automatic GitHub issue closure, leaving the PR open for external review, or local merge with manual state syncing to GitHub. Worktree cleanup occurs after merge operations.

Do I need completed implementation checklists before closing a GitHub issue?▼

Yes, pre-closure validation requires fully completed implementation checklists, passing test suites, and the removal of the in-progress label before allowing any GitHub issue closure work to proceed.

Can I leave a PR open for external review while syncing local merge state to GitHub?▼

Yes, you can leave the PR open for external review or perform a local merge with manual state syncing to GitHub. Both paths still execute pre-closure test verification and worktree cleanup after merge operations.

Related Skills

Explore More Software Engineering Skills→
GGPromptsGGPrompts
147

merge

Merge feature branches into main and clean up worktrees using Git.

Community
Advanced
jonnytacos8jonnytacos8

merge-pr

Squash merge prepared GitHub PRs with head-commit verification and worktree cleanup.

Community
Advanced
romeerezromeerez
543

repro

Automates creation of failing test cases for Orchid ORM issues from GitHub.

Community
Intermediate
SignmanalSignmanal
1

github-issues

Manage GitHub issue lifecycles via gh CLI or REST API.

Community
Intermediate