skills.rest
astrosteveo
astrosteveoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

finishing-a-development-branch

Run project tests, update documentation, and create a PR-ready summary.

Updated Aug 23, 2026
Search Tags:#git#documentation#pr#tests#finish#development-branch
One-click install
npx skills add https://github.com/astrosteveo/marketplace --skill finishing-a-development-branch-astrosteveo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/astrosteveo/marketplace/tree/main/plugins/superpowers/skills/finishing-a-development-branch
Command: npx skills add https://github.com/astrosteveo/marketplace --skill finishing-a-development-branch-astrosteveo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams finish feature work by validating tests, updating documentation, and preparing a PR, reducing handoffs and rework.

Core Features & Use Cases

  • Verify feature branch and ensure you’re not on main or master.
  • Run tests across the project and proceed only if all tests pass.
  • Update relevant docs (CLAUDE.md, PRD.md / GDD.md, README.md) to reflect changes and release readiness.
  • Create a PR with a concise summary and a clear test plan, enabling review and integration.
  • Provide options for PR flow (review, merge, or keep branch) and perform cleanups after merge.

Quick Start

Use this skill to finish a development feature by running tests, validating results with the user, and creating a PR with updated documentation.

Frequently Asked Questions about finishing-a-development-branch

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

FAQPage Schema
How do I finish a git development branch and prepare it for a PR?▼

To finish a git development branch, you verify the feature branch, run the project test suite, update relevant documentation, and generate a PR-ready summary with a clear test plan.

What documentation do I need to update before creating a pull request?▼

Before creating a pull request, you should update relevant docs such as CLAUDE.md, PRD.md or GDD.md, and README.md to reflect feature changes and ensure release readiness.

Can I use this workflow to run tests before finishing a feature branch?▼

Yes, the workflow runs tests across the project and prompts for manual validation, proceeding to PR creation only if all tests pass successfully.

What happens if my feature branch tests fail during final verification?▼

If tests fail during final verification, the workflow stops before PR creation, preventing incomplete feature work from moving forward to code review and integration.

Does this process verify I am not committing changes directly to main?▼

Yes, the process verifies your feature branch and ensures you are not on main or master before running tests and preparing documentation for the pull request.

What options are available after merging a pull request?▼

After merging, options include reviewing, merging, or keeping the branch, and the workflow performs cleanups to finalize the development branch lifecycle.

Related Skills

Explore More Software Engineering Skills→
hojinzshojinzs
16

push

Publish verified local commits to a remote Git branch with pre-push validation.

Community
Intermediate
ultramaxoAIultramaxoAI

finishing-a-development-branch

Verify tests and execute merge or cleanup for feature branches.

Official
Intermediate
selcukyucelselcukyucel
1

prompt-test

Run a prompt against test inputs and score outputs with a binary rubric.

Community
Advanced
Archive228Archive228
746

pr-from-diff

Generate structured pull request descriptions from commit messages and changes.

Community
Basic