graphite-skill

Delegate verbose Git and Graphite CLI commands to isolated subagents.

61|3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/joelhooks/joelclaw --skill graphite-skill-joelhooks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphite-skill
Source: https://github.com/joelhooks/joelclaw/tree/main/.agents/skills/graphite-skill
Command: npx skills add https://github.com/joelhooks/joelclaw --skill graphite-skill-joelhooks

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill eliminates the overwhelming verbosity of Git and Graphite CLI commands, preventing context window exhaustion and enabling more efficient AI-assisted development.

Core Features & Use Cases

  • Automatic Delegation: Verbose git/Graphite commands are automatically delegated to isolated subagents.
  • Context Efficiency: Reduces token consumption from thousands to under 50 per operation.
  • Use Case: When you ask Claude to "check my Graphite stack," it automatically delegates the verbose gt stack command to a subagent, returning a concise summary like "✓ feature/auth | 3 PRs | Review #456" instead of 15KB of raw JSON.

Quick Start

Ask Claude to check your Graphite stack.

Frequently Asked Questions about graphite-skill

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

FAQPage Schema
How do I reduce token consumption when running git commands in an AI coding environment?

Reduce token consumption by delegating verbose git commands to isolated subagents that return concise summaries. This prevents context window exhaustion by shrinking raw CLI output from thousands of tokens to under 50 per operation.

What is the best way to manage Graphite stacks without cluttering my AI assistant's context?

Manage Graphite stacks by automatically delegating CLI operations like `gt stack` to subagents. This intercepts verbose JSON output and returns brief summaries, keeping the main AI context clean for development tasks.

Why does running git log or git diff exhaust my AI coding context window?

Git log and git diff exhaust context windows because they generate massive raw text output. Delegating these commands to isolated subagents captures the output separately and returns only concise summaries to the main context.

Can I automate git workflow delegation without manually writing subagent prompts?

Yes, you can automate git workflow delegation using built-in patterns that intercept common commands like `gt stack`, `git log`, and `git diff`, automatically routing them to subagents without manual prompt engineering.

Does this context-efficient git workflow approach work with standard Git commands or only Graphite?

This approach works with both standard Git commands and Graphite CLI operations. It supports automatic delegation patterns for common git commands as well as Graphite-specific commands like `gt stack`.

What are the limitations of using subagents for git and Graphite CLI operations?

Subagents for git and Graphite CLI operations are limited to returning concise summaries, meaning raw detailed output is abstracted away. Users requiring full, untruncated CLI output for deep debugging may find the summarized context insufficient.