finishing-a-development-branch

Validate tests, builds, and lint before merging or discarding a development branch.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/danilonovaisv/PROMPT-APP --skill finishing-a-development-branch-danilonovaisv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/danilonovaisv/PROMPT-APP/tree/main/.agent/skills/finishing-a-development-branch
Command: npx skills add https://github.com/danilonovaisv/PROMPT-APP --skill finishing-a-development-branch-danilonovaisv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing development branches is essential to keep the mainline stable and ensure work is properly reviewed, merged, or discarded after feature completion.

Core Features & Use Cases

  • Verification workflow: run tests, build, and lint to guarantee quality before finalization.
  • Decision framework: present options to merge to main, open a pull request, keep the branch for later work, or discard obsolete work.
  • Clean-up rigor: summarize changes, ensure documentation is up to date, and remove temporary worktrees or branches to maintain repository hygiene.

Quick Start

Run the finishing workflow to verify, consolidate, and finalize the current feature branch.

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 finalize a git branch before merging to main?

Finalizing a git branch requires running npm test, npm run build, and npm run lint to validate quality. This workflow compares diffs, summarizes changes, and presents options to merge, open a PR, keep, or discard the branch.

What is the best workflow to verify code quality before creating a pull request?

A code quality workflow enforces npm test, npm run build, and npm run lint checks before a pull request. It evaluates branch diffs and provides clear finalization options with guardrails to ensure merge-ready confidence.

When should I discard or keep a development branch after feature work?

Deciding to keep or discard a development branch depends on test and build validation results. If checks pass, you can merge or open a PR; if obsolete, the workflow guides branch removal to maintain repository hygiene.

Does this branch finishing process run npm test and lint checks automatically?

Yes, the branch finishing process automatically enforces npm test, npm run build, and npm run lint checks. It uses these guardrails to validate tests, builds, and code quality before presenting finalization options.

How do I clean up temporary worktrees and branches after merging a feature?

Post-merge cleanup involves summarizing changes, ensuring documentation is updated, and removing temporary worktrees or branches. This maintains repository hygiene after discarding obsolete work or completing a feature merge.

Can I use this workflow for bug fixes and post-merge cleanup in PROMPT-APP?

Yes, this workflow applies to feature work, bug fixes, and post-merge cleanup in PROMPT-APP. It validates builds and tests, then guides whether to merge, create a PR, keep, or discard the branch.