start

Create a Graphite branch with a normalized jm/ prefix using gt.

8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jfmyers9/agent --skill start-jfmyers9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/jfmyers9/agent/tree/main/skills/start
Command: npx skills add https://github.com/jfmyers9/agent --skill start-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a Graphite branch to organize and isolate new work, reducing context switching and merge conflicts.

Core Features & Use Cases

  • Parse and validate a provided branch name.
  • Normalize branch name to jm/ prefix if missing.
  • Check for uncommitted changes and continue safely.
  • Create the Graphite branch using gt create <branch-name>.
  • Use Case: starting work on a feature like '/skill:start feature-x' to begin a new Graphite branch.

Quick Start

Provide a branch name to start work on, for example '/skill:start feature-x'.

Frequently Asked Questions about start

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

FAQPage Schema
How do I start a new feature branch with Graphite?

To start a new feature branch with Graphite, provide a branch name to the Skill. It normalizes the name with a jm/ prefix and uses the gt create command to branch your work, even with uncommitted changes present.

Can I create a Graphite branch if I have uncommitted changes?

Yes, you can create a Graphite branch with uncommitted changes. The Skill checks for uncommitted changes and continues safely, allowing you to isolate new work without stashing your current progress first.

What is the best way to normalize branch names for a Graphite workflow?

The best way to normalize branch names for a Graphite workflow is using this Skill, which automatically parses and validates your input, adding the required jm/ prefix if missing before creating the branch.

Do I need Bash to use Graphite for branching?

Yes, you need a Bash environment to use this Graphite branching Skill. It relies on Bash to execute the gt create command, parse arguments, and provide post-creation guidance for your new feature branch.

Why does my Graphite branch creation fail without a jm/ prefix?

Graphite branch creation requires a jm/ prefix for name normalization. This Skill handles the prefix automatically during argument parsing, ensuring your branch name is valid before executing the gt create command.

How does creating a Graphite branch reduce merge conflicts?

Creating a Graphite branch isolates new work into a separate branch, reducing context switching and merge conflicts. This organization keeps your main branch clean and integrates features systematically.