project-orchestrator:finishing-branch

Coordinate testing, changelogs, and PR workflows across mono- and polyrepo projects.

Updated Feb 15, 2026

Search Tags:#automation #git #changelog #branch #pull-request #tests #finish

Ready to run

npx skills add https://github.com/GigaFyde/project-orchestrator --skill project-orchestrator-finishing-branch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-orchestrator:finishing-branch
Source: https://github.com/GigaFyde/project-orchestrator/tree/main/skills/finishing-branch
Command: npx skills add https://github.com/GigaFyde/project-orchestrator --skill project-orchestrator-finishing-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the finalization of development work by validating tests, preparing changelogs, ordering multi-service PRs, and cleaning up worktrees, enabling repeatable, safe merges.

Core Features & Use Cases

Enforces pre-merge test verification across mono- and polyrepo structures.
Automates changelog integration when configured and guides per-service PR sequencing.
Handles base-branch rebases, conflict guidance, and post-finish cleanup to ensure clean states.
Supports both monorepo and polyrepo layouts, adapting steps to service-level worktrees.

Quick Start

After implementing a feature, run the finishing-branch process to verify tests, create optional changelog entries, and present PR options.

Frequently Asked Questions about project-orchestrator:finishing-branch

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

FAQPage Schema

How do I automate pull request creation and changelog updates when finishing a branch?▼

Automating pull request creation and changelog updates when finishing a branch involves coordinating pre-merge test verification, preparing changelog entries, and ordering multi-service PRs. This process streamlines finalizing development work by validating tests and presenting PR options to ensure safe, repeatable merges.

What is the best way to sequence pull requests across a polyrepo project?▼

Sequencing pull requests across a polyrepo project requires guiding per-service PR ordering based on service-level worktrees. The finalization process adapts to multi-service setups, handling base-branch rebases and conflict guidance to coordinate PR workflows across repositories for clean, auditable finishes.

How do I handle base-branch rebases and merge conflicts before opening a pull request?▼

Handling base-branch rebases and merge conflicts before opening a pull request requires guidance during the branch finalization process. The workflow coordinates base-branch rebase operations, provides conflict guidance, and enforces post-finish cleanup to ensure worktrees remain in clean states before merging.

Can I enforce pre-merge test validation across both monorepo and polyrepo layouts?▼

Pre-merge test validation can be enforced across both monorepo and polyrepo layouts. The finalization workflow validates tests before merging, adapting its steps to service-level worktrees to support multi-service setups and ensure repeatable, safe merges across different repository structures.

Does automated branch finishing support auto-deploy warnings and audit trails?▼

Automated branch finishing supports auto-deploy warnings and records living-state outcomes for auditable finishes. It enforces pre-merge validations and provides auto-deploy warnings to ensure safe merges, maintaining an auditable record of the finalization process.

When should I not use automated branch finalization for pull requests?▼

Automated branch finalization for pull requests should not be used when manual intervention is required for complex conflict resolution beyond basic guidance. The process enforces pre-merge validations and handles cleanups, but severe conflicts may require manual handling outside the automated workflow.