skills.rest
oporpino
oporpinoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

br4zz4:finish

Verifies tests and integrates completed work via PR, merge, or discard.

Updated May 25, 2025
Search Tags:#git#testing#code review#pull request#worktree#merge#branch
One-click install
npx skills add https://github.com/oporpino/commons --skill br4zz4-finish-oporpino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: br4zz4:finish
Source: https://github.com/oporpino/commons/tree/main/ai/shared/skills/br4zz4%3Afinish
Command: npx skills add https://github.com/oporpino/commons --skill br4zz4-finish-oporpino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an implementation is finished, developers often skip test verification, forget documentation updates, or leave stale branches and worktrees behind. This Skill enforces a disciplined finish workflow so work is integrated safely and nothing is merged with failing tests. ## Core Features & Use Cases - Test Gate: Runs the full test suite first and blocks any merge or PR until all tests pass. - Documentation Sync: Applies documentation rules before opening a PR, updating business rule files and learnings under .project/docs/. - Integration Options: Presents four choices — open a PR, merge locally into main, keep the branch, or discard the work with typed confirmation. - Worktree Cleanup: Removes parallel git worktrees under $HOME/workspace/.worktrees/ only when work is integrated or has no uncommitted changes. - Use Case: After completing a feature branch, invoke this Skill to verify tests, update docs, push the branch, open a PR, and optionally trigger a code review request. ## Quick Start Ask the assistant to finish the current implementation by verifying tests and presenting integration options for the completed branch.

Frequently Asked Questions about br4zz4:finish

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

FAQPage Schema
How do I safely merge a finished feature branch into main?▼

Run the full test suite first and only proceed if all tests pass. Then either open a pull request or merge locally with git checkout main, git pull --rebase, and git merge, re-running tests on the merged result before deleting the branch.

What should I do before opening a pull request?▼

Verify all tests pass, update documentation for any changed business rules or learnings, commit the doc changes, then push the branch and create the PR. After opening it, consider triggering a code review request.

Can I merge code when tests are failing?▼

No. The workflow blocks any merge or PR when tests fail and requires fixing the failures first. This rule has no exceptions — never merge with failing tests.

How do I clean up git worktrees after parallel work?▼

Remove worktrees under the workspace .worktrees directory only when the work is integrated or the worktree has no uncommitted changes. Worktrees with uncommitted work are kept with a warning, then run git worktree prune.

How do I discard a branch without losing work accidentally?▼

Discarding requires explicit typed confirmation after showing the branch name and commits to be deleted. Only after exact confirmation does the workflow delete the branch with git branch -D.

Related Skills

Explore More Software Engineering Skills→
laststancelaststance
1

bulk-issues

Automate bulk resolution of open GitHub issues on a single feature branch.

Official
Advanced
tribedotruntribedotrun
8

mando-pr

Create GitHub pull requests and trigger AI reviewers with CI monitoring.

Official
Advanced
kevinslinkevinslin
6

dev.document

Record documentation changes across README.md, DESIGN.md, CLAUDE.md, AGENTS.md, and NEXT_STEPS.md.

Community
Basic
hung-phanhung-phan

trunk-based-development

Implement a trunk-based development workflow with short-lived branches and feature flags.

Community
Advanced