branching-and-pr-safety

Enforces Git branch naming, PR test plans, and safe upstream sync.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/roaming-rockenfels/ghostfolio --skill branching-and-pr-safety
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branching-and-pr-safety
Source: https://github.com/roaming-rockenfels/ghostfolio/tree/main/.claude/skills/branching-and-pr-safety
Command: npx skills add https://github.com/roaming-rockenfels/ghostfolio --skill branching-and-pr-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all code changes are managed safely and efficiently within a Git repository, preventing common errors and enforcing best practices for branching and pull requests.

Core Features & Use Cases

  • Branch Naming Enforcement: Guarantees branches adhere to predefined naming conventions (e.g., feature/, fix/, sync/).
  • Safe Pushing: Prevents accidental force-pushes to critical branches and ensures correct remote targets.
  • PR Test Plan Generation: Automates the creation of pull requests with mandatory test plans, ensuring code quality and validation.
  • Upstream Sync Safety: Provides guardrails for synchronizing with upstream repositories, minimizing merge conflicts and accidental overwrites.
  • Use Case: Before submitting your code for review, use this Skill to automatically verify your branch name, ensure your PR includes a comprehensive test plan, and confirm you're pushing to the correct remote, safeguarding your repository's integrity.

Quick Start

Use the branching and PR safety skill to prepare your changes for a pull request.

Frequently Asked Questions about branching-and-pr-safety

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

FAQPage Schema
How do I enforce branch naming conventions in a Git workflow?

To enforce branch naming conventions in a Git workflow, this Skill validates branch names against predefined prefixes like feature/, fix/, or sync/ before operations. It automatically checks naming standards to guarantee adherence to project conventions.

How do I prevent accidental force-pushes to critical Git branches?

To prevent accidental force-pushes to critical Git branches, this Skill implements safe pushing guardrails that verify correct remote targets. It blocks dangerous operations to secure your repository's integrity during synchronization.

Does this PR safety Skill require both Git CLI and GitHub CLI?

Yes, this PR safety Skill requires both Git CLI and GitHub CLI for execution. It mandates these dependencies to manage branches, generate pull requests with test plans, and implement upstream-sync safety checks.

How do I automatically generate a pull request with a mandatory test plan?

To generate a pull request with a mandatory test plan, this Skill automates PR creation while enforcing test plan inclusion. It ensures code quality validation by mandating comprehensive test plans before submission.

What is the best way to safely sync a private fork with an upstream repository?

To safely sync a private fork with an upstream repository, this Skill provides upstream-sync safety checks that minimize merge conflicts and prevent accidental overwrites. It enforces guardrails within a private-fork/upstream model.

What happens if my branch name does not match project conventions?

If your branch name does not match project conventions, the Skill will flag the violation during preparation for a pull request. Branch naming enforcement guarantees branches adhere to predefined naming conventions before code review.