Rebase

Block git rebase commands to prevent history rewriting and data loss.

39|6|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/the-agency-ai/the-agency --skill rebase-the-agency-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Rebase
Source: https://github.com/the-agency-ai/the-agency/tree/main/.claude/skills/rebase
Command: npx skills add https://github.com/the-agency-ai/the-agency --skill rebase-the-agency-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents the use of the potentially destructive git rebase command to safeguard repository history and data integrity.

Core Features & Use Cases

  • Command Blocking: Enforces framework-wide prohibition of git rebase commands via hookify rules.
  • Error Prevention: Prevents accidental history rewriting and data loss in multi-worktree monorepos.
  • Use Case: When a developer tries to run git rebase, it is blocked automatically, ensuring safe branch synchronization through merges instead.

Quick Start

Use the rebase skill to ensure that rebase commands are automatically prevented when working on sensitive repositories.

Frequently Asked Questions about Rebase

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

FAQPage Schema
How do I prevent accidental history rewriting with git rebase?

To prevent accidental history rewriting with git rebase, you can use a command blocking framework that enforces hookify rules to automatically intercept and block rebase commands, ensuring repository integrity. This avoids data loss in complex multi-worktree setups.

What happens when git rebase is blocked in a version control workflow?

When git rebase is blocked in a version control workflow, developers are prevented from rewriting history and must use merges for safe branch synchronization instead. This ensures repository integrity and prevents data loss in complex multi-worktree setups.

Can I block git rebase commands in a multi-worktree monorepo?

Yes, you can block git rebase commands in a multi-worktree monorepo by applying hookify rules through a command blocking framework. This prevents accidental history rewriting and data loss, ensuring safe branch synchronization through merges instead.

Why should I stop using git rebase for branch synchronization?

You should stop using git rebase for branch synchronization because it rewrites repository history and risks data loss, especially in multi-worktree setups. Blocking rebase commands enforces safe merges instead, maintaining repository integrity.

Does this command blocking approach work with standard version control environments?

Yes, this command blocking approach works with standard version control environments by integrating seamlessly into development setups via hookify rules. It enforces restrictions automatically when developers attempt to run git rebase on sensitive repositories.