superpowers-finish

Verify tests, lint, and documentation before merging or discarding a development branch.

Updated Apr 4, 2026

Search Tags:#workflow #verification #cleanup #merge #branch #pr #finish

Ready to run

npx skills add https://github.com/susantosanto/config-opencode --skill superpowers-finish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpowers-finish
Source: https://github.com/susantosanto/config-opencode/tree/main/skills/superpowers-finish
Command: npx skills add https://github.com/susantosanto/config-opencode --skill superpowers-finish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finalize a development branch by verifying completion tasks and applying cleanup and merge/PR decisions.

Core Features & Use Cases

Verifies tests pass, lint clean, and documentation updates.
Presents options: merge to main, create a PR for review, keep the branch for later, or discard the branch.
Example: after all tasks are done, run this skill to ensure readiness before merging changes to the main branch.

Quick Start

Invoke the superpowers-finish skill to finalize the current development branch.

Frequently Asked Questions about superpowers-finish

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

FAQPage Schema

How do I finalize a development branch with proper verification and cleanup?▼

To finalize a development branch, you can run a workflow that verifies tests pass, checks lint, and confirms documentation updates before presenting merge or PR options. This ensures strict post-task actions and branch hygiene.

What steps should I take to ensure branch readiness before merging to main?▼

Branch readiness involves verifying that all tests pass, linting is clean, and documentation is updated. You then evaluate safe, deterministic steps and guardrails to prevent accidental data loss before merging to main.

What is the best way to manage branch cleanup and PR decisions after completing tasks?▼

The best way to manage branch cleanup is to use a workflow that presents options: merge to main, create a PR for review, keep the branch for later, or discard it, ensuring safe and deterministic finalization.

Can I keep a development branch for later instead of merging or creating a PR?▼

Yes, you can keep a development branch for later. The finalization workflow presents multiple options, including keeping the branch, merging to main, creating a PR, or discarding it entirely.

Does branch finalization include guardrails to prevent accidental data loss?▼

Yes, branch finalization includes guardrails to prevent accidental data loss. It formats safe, deterministic steps to ensure strict post-task actions are applied without risking your codebase.

When should I not use an automated branch finalization workflow?▼

You should avoid automated branch finalization when your software workflow does not require strict post-task actions or branch hygiene, as it enforces deterministic steps and verification checks before merge or PR decisions.