git-repoint-branch

Extracts specified files, directories, or glob patterns from a feature branch to a new branch targeting main.

2|Updated Nov 6, 2015
One-click install
npx skills add https://github.com/ahoym/dotfiles --skill git-repoint-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-repoint-branch
Source: https://github.com/ahoym/dotfiles/tree/main/.claude/commands/git-repoint-branch
Command: npx skills add https://github.com/ahoym/dotfiles --skill git-repoint-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you isolate specific changes from a feature branch into a new, clean branch, making it easier to create focused pull requests and manage complex development workflows.

Core Features & Use Cases

  • Branch Refactoring: Extract independent changes from a compound branch into a new PR targeting main.
  • Selective Commits: Allows users to specify files, directories, or glob patterns to include in the new branch.
  • Use Case: You've made several unrelated changes on a feature branch. Use this Skill to extract just the UI-related changes into a new branch for a dedicated UI-focused PR, keeping your original branch clean for other tasks.

Quick Start

Use the repoint-branch skill to extract the '.claude/guidelines/' directory to a new branch named 'feature/guidelines-lite'.

Frequently Asked Questions about git-repoint-branch

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

FAQPage Schema
How do I extract specific files from a git branch into a new branch?▼

Extract specific files from a git branch by specifying files, directories, or glob patterns to isolate independent changes. The tool validates these changes for independence and creates a clean branch targeting main.

Can I split a feature branch into multiple pull requests by directory?▼

Split a feature branch into multiple pull requests by using glob patterns or directories to extract independent changes. This isolates specific modifications into a new branch, enabling focused pull requests targeting main.

What is the best way to separate unrelated code changes in git for code management?▼

Separate unrelated code changes by extracting independent modifications from a compound feature branch into a new branch. This refactoring approach validates change independence and keeps your original branch clean for other tasks.

Does branch refactoring validate if changes are independent before extracting?▼

Branch refactoring validates changes for independence before extraction to ensure the new branch only contains isolated modifications. This prevents extracting dependent code that might break the main branch target.

Can I create a pull request automatically after extracting changes to a new branch?▼

Create a pull request automatically after extracting changes because the tool offers PR creation upon successful branch extraction. This streamlines the workflow from branch refactoring directly to pull request submission.

Why should I extract changes to a new branch instead of keeping them in the feature branch?▼

Extract changes to a new branch to create focused pull requests and manage complex development workflows. Keeping unrelated changes in a single feature branch complicates code management and pull request reviews.