skills.rest
kriscendobot
kriscendobotCOMMUNITY
Explore all skills by this author →
GitHub

frozen-base-branch

Create and maintain frozen base branches for fork-side pull requests.

3|2|Updated May 12, 2026
Search Tags:#automation#git#workflow#pull-request#version-control#rebasing
One-click install
npx skills add https://github.com/kriscendobot/garden --skill frozen-base-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frozen-base-branch
Source: https://github.com/kriscendobot/garden/tree/main/skills/frozen-base-branch
Command: npx skills add https://github.com/kriscendobot/garden --skill frozen-base-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill prevents the common issue where pull requests become cluttered or difficult to manage due to the constant drift of the upstream base branch, ensuring that your review environment remains stable and predictable.

Core Features & Use Cases

  • Snapshot Isolation: Creates a frozen snapshot of the upstream branch at the moment of PR creation, allowing work to proceed against a fixed point in time.
  • Atomic Rebase Management: Automatically updates both the base and head branches during rebase operations to maintain consistency.
  • Use Case: When working on a long-running feature in a fork, use this skill to ensure your PR remains focused on your specific changes rather than being affected by unrelated commits landing in the upstream repository.

Quick Start

Instruct the garden to initialize a frozen base branch for the current pull request to isolate it from upstream changes.

Frequently Asked Questions about frozen-base-branch

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

FAQPage Schema
How do I isolate a pull request from upstream trunk drift?▼

Isolating a pull request from upstream trunk drift involves creating and maintaining frozen base branches based on specific commit SHAs. This ensures your review environment remains stable and predictable despite unrelated upstream commits.

Why does my pull request keep getting cluttered with unrelated commits from the upstream base branch?▼

Your pull request gets cluttered because the upstream base branch constantly drifts while you are working. Using a frozen base branch snapshot isolates your PR development from this continuous upstream repository drift.

Do I need GitHub CLI to manage frozen base branches for fork-side pull requests?▼

Yes, you need GitHub CLI and standard git tooling to manage frozen base branches for fork-side pull requests. These dependencies are required to perform the atomic branch rebasing and cleanup operations that maintain consistency.

What is the best way to manage atomic rebasing when updating a long-running feature branch?▼

The best way to manage atomic rebasing for a long-running feature branch is to automatically update both the base and head branches during rebase operations. This maintains consistency and keeps your PR focused on specific changes.

When should I snapshot the upstream branch to isolate my git workflow?▼

You should snapshot the upstream branch at the moment of PR creation to isolate your git workflow. This creates a fixed point in time, ensuring work proceeds against a stable base rather than being affected by constant upstream drift.

Related Skills

Explore More Software Engineering Skills→
LynxLabVNLynxLabVN

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merging.

Official
Advanced
Yeachan-HeoYeachan-Heo
32.6k

git-master

Coordinate Git workflows for atomic commits, interactive rebasing, and history cleanup.

Community
Intermediate
mathiasbourgoinmathiasbourgoin
2

git-conventions

Standardize git commit messages, branch names, and pull request descriptions.

Community
Intermediate
mirakuimirakui

git-push-pr

Push a feature branch and create or update pull requests via git and gh commands.

Community
Intermediate