finishing-a-development-branch-extras

What problem does it solve?

This Skill eliminates common failures when finishing development branches, such as blocked pull request creation, incorrect version bump ordering in semantic release workflows that cause artifact mismatches, incomplete completion checks that miss independent review findings, and messy conflict resolution after rebases or squash merges.

Core Features & Use Cases

• Reliable PR Creation: Provides a first-class gh api fallback when gh pr create is blocked, plus pre-checks for existing PRs and valid remote base branches to avoid errors.
• Correct Release Workflow Ordering: Enforces that version bumps run before artifact builds in semantic release pipelines to prevent mismatched version artifacts.
• Scoped Completion Validation: Requires reconciling all independent review artifacts before declaring work complete, avoiding false readiness claims.
• Conflict Resolution Best Practices: Includes clear rules for rebase vs merge conflict handling, stale PR conflict state fixes, and cleanup of long-lived or squash-merged branches. Use Case: For a developer working on a feature branch with a semantic release CI pipeline, this Skill ensures PRs are created reliably, release artifacts have correct versions, and branch conflicts are resolved without breaking commit signatures or linear history.

Quick Start

Use the finishing-a-development-branch-extras skill to create a pull request for your current feature branch, enforce correct version bump ordering in your release workflow, and resolve any rebase conflicts before merging to main.