grimoire-branch-guard

Create a clean, feature-based git branch before drafting new features.

Updated Jan 26, 2025
One-click install
npx skills add https://github.com/jlissner/lissner.io --skill grimoire-branch-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grimoire-branch-guard
Source: https://github.com/jlissner/lissner.io/tree/main/.claude/skills/grimoire-branch-guard
Command: npx skills add https://github.com/jlissner/lissner.io --skill grimoire-branch-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a clean, appropriately named git branch before starting a new feature, preventing piggy-backing on an in-progress branch or a dirty tree.

Core Features & Use Cases

  • Preconditions: Project is a git repository and your working directory is at the project root.
  • Workflow: Snapshot the branch state, classify the situation, propose a branch name, create the new branch, and hand off to grimoire-draft by updating the manifest frontmatter.
  • Triggers & Routing: Activated when a user requests a new feature; if the current branch is dirty or misaligned, the guard blocks drafting until a clean branch is created.

Quick Start

Enable the grimoire branch guard before drafting to create a clean, appropriately named branch.

Frequently Asked Questions about grimoire-branch-guard

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

FAQPage Schema
How do I prevent starting a new git feature on a dirty or in-progress branch?

To prevent starting a new git feature on a dirty branch, use a branch guard to snapshot the current state, classify the tree, and block drafting until a clean branch is created. This avoids piggy-backing on in-progress work.

How do I automatically suggest a properly named git branch before starting development?

You can automatically suggest a properly named git branch by using a workflow guardrail that detects your current branch state and proposes a feature-based branch name. It then confirms with you before creating the new branch.

What is the best way to enforce git branch naming conventions for new features?

The best way to enforce git branch naming conventions is to apply a guardrail that proposes a standardized feature branch name and blocks new feature drafting until the clean, appropriately named branch is created.

Do I need a clean working directory to create a new feature branch with branch guardrails?

Yes, you need a clean working directory at the project root in an initialized git repository. The branch guard checks for a dirty tree or misaligned branch and blocks creation until the repository is clean.

Why does my feature drafting workflow require a clean git branch?

Feature drafting requires a clean git branch to prevent mixing unrelated changes. The branch guard blocks drafting on dirty or misaligned branches, ensuring new work starts isolated on a properly named feature branch.

Can grimoire-branch-guard block drafting if my git tree is dirty?

Yes, grimoire-branch-guard blocks drafting if your git tree is dirty or the current branch is misaligned. It requires a clean working directory, suggests a new branch name, and confirms before proceeding.