finishing-a-development-branch-extras

Resolve GitHub branch finishing failures with gh api fallback and release sequencing.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/ByronWilliamsCPA/.claude --skill finishing-a-development-branch-extras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch-extras
Source: https://github.com/ByronWilliamsCPA/.claude/tree/main/.claude/skills/finishing-a-development-branch-extras
Command: npx skills add https://github.com/ByronWilliamsCPA/.claude --skill finishing-a-development-branch-extras

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about finishing-a-development-branch-extras

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

FAQPage Schema
How do I fix blocked pull request creation on GitHub when gh pr create fails?

Fix blocked pull request creation on GitHub by using a first-class gh api fallback to bypass failures when gh pr create is blocked, ensuring PRs are created reliably after pre-checking for existing PRs and valid remote base branches.

Why does my semantic release CI pipeline produce mismatched version artifacts?

Semantic release CI pipelines produce mismatched version artifacts when version bumps run after artifact builds, so enforcing version-bump-before-build sequencing in your release workflow prevents incorrect version mismatches in built artifacts.

What is the best way to resolve rebase conflicts after a squash merge without breaking commit signatures?

Resolving rebase conflicts after a squash merge without breaking commit signatures requires applying correct rebase conflict resolution strategies that preserve linear history while cleaning up long-lived or squash-merged branches properly.

Can I validate branch completion against all independent review artifacts before merging to main?

You can validate branch completion against all independent review artifacts before merging to main by enforcing scoped completion checks that require reconciling every independent review finding, avoiding false readiness claims before declaring work complete.

Do I need to check for existing PRs and valid remote base branches before creating a pull request?

You need to pre-check for existing PRs and valid remote base branches before creating a pull request to avoid errors and ensure reliable PR creation, which prevents duplicate PRs and invalid base branch failures.