Graphite
Graphite CLI detection and stacked PR workflow management
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill Graphitegit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/graphite ~/.claude/skills/GraphitePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Graphite Skill
> Auto-detect Graphite CLI and enable stacked PR workflows.
**Key Principle**: Detect once, ask once, remember forever.
---
## Overview
Graphite CLI (`gt`) enables stacked pull requests - a series of PRs where each depends on the previous one. This allows breaking large features into smaller, reviewable pieces.
**Why Stacked PRs?**
- Large features (500+ lines) broken into reviewable pieces (<200 lines)
- Each PR reviewed independently
- Merge progressively as approved
- Easier to isolate issues and rollback
---
## When to Use
**Trigger Detection**:
- During PR creation workflows
- When user says "create stacked PR"
- First commit operation in a new repo
**Trigger Workflow**:
- `/v-graphite:detect` - Check for CLI and set preference
- `/v-graphite:stack` - Create/manage stacked PRs
---
## Commands
| Command | Purpose |
|---------|---------|
| `/v-graphite:detect` | Check for gt CLI and save preference |
| `/v-graphite:stack` | Create or manage stacked PRs |
---
## Detection Flow
```
1. Check if gt command exists
↓
2. Check stored preference
├─ YES → Use stored preference
└─ NO ↓
3. Ask user: "Enable Graphite workflow?"
↓
4. Save preference to .claude/settings.json
↓
5. Never ask again
```
### Preference Storage
**Repo-level** (team preference):
```json
// .claude/settings.json
{
"skills": {
"git": {
"graphite": {
"enabled": true,
"detected_version": "1.4.2"
}
}
}
}
```Details
- Skill name
Graphite- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/graphite/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Graphite skill do?
Graphite CLI detection and stacked PR workflow management
How do I install the Graphite skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Graphite popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
PR Feedback Training First Loop
8Freddy-CHEN-ux/00_claude_skills
Extract, learn, and integrate PR feedback into the Violet brain
Git Writer
8Freddy-CHEN-ux/00_claude_skills
Safe workflow for git write operations (git rm). Use for removing files from git.
PR Writer
5vnovakovits/claude-skills
Write, scope, size, and review pull requests that are fast and safe to review and merge. Grounded in Google's Engineering Practices, GitHub's PR guidance, the SmartBear/Cisco review study, Conventional Commits, LLVM's AI tool policy and agentic-PR research, plus delivery practice (expand/contract migrations, flags, observability gates). Covers splitting and sizing, Conventional-Commit titles, a stand-alone description (what/why, Mermaid diagrams of only what changed: Example Mapping for a policy, Event Storming for a process, sequence for an interaction, contracts crossed, confidence card, tes
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.