gt:submit

Push a Graphite stack and create or update GitHub pull requests.

1|1|Updated Apr 24, 2026

Search Tags:#automation #git #pull request #graphite #github cli #submission #stack restacking

Ready to run

npx skills add https://github.com/luan/agents --skill gt-submit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gt:submit
Source: https://github.com/luan/agents/tree/main/plugins/gt/skills/submit
Command: npx skills add https://github.com/luan/agents --skill gt-submit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, error-prone steps of pushing a Graphite stack and creating or updating GitHub pull requests so you get the right PRs without juggling git and gh commands.

Core Features & Use Cases

Stack submission with safe defaults: Uses an update-only default mode to reduce accidental PR creation for WIP branches.
Conflict-aware flow: Checks stack health first and instructs restacking when divergence or conflicts require it.
Grounded PR updates: Fetches the current PR title/body and then regenerates descriptions so they align with the final branch diff while preserving grounded context.
Clear reporting: Reports Graphite app links only, keeping outcomes consistent with the Graphite workflow.

Quick Start

Run gt submit to push the Graphite stack and create or update the relevant pull requests with correctly refreshed PR descriptions.

Frequently Asked Questions about gt:submit

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

FAQPage Schema

How do I automate pushing a Graphite stack and creating GitHub pull requests?▼

You can automate submitting a Graphite stack by running a single command that pushes the stack and creates or updates corresponding GitHub pull requests, eliminating manual git and gh commands. This skill handles the push and PR creation automatically.

Can I update an existing GitHub pull request when pushing new commits to a Graphite stack?▼

Yes, when pushing updates to a Graphite stack, this skill updates existing GitHub pull requests. It fetches the current PR title and body, then regenerates descriptions to align with the final branch diff while preserving grounded context.

Does this Graphite stack submission workflow prevent accidental PR creation for WIP branches?▼

Yes, this workflow uses an update-only default mode to reduce accidental PR creation for WIP branches. This safe default ensures pull requests are only updated rather than newly created unless explicitly intended.

Why do I need to restack my Graphite stack before submitting a pull request?▼

Restacking is required when stack health checks reveal branch divergence or conflicts. This skill detects these issues during submission and instructs you to restack before it can successfully push and create or update pull requests.

What is the best way to refresh GitHub PR descriptions after updating a branch in a Graphite stack?▼

The best way to refresh PR descriptions is using a grounded update flow that fetches current PR data via gh pr view JSON fields, then regenerates the description to match the final branch diff while preserving original context.