Menu
Manage stacked pull requests using Graphite CLI. Create, submit, and restack PR chains.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Run initial OmniClaw setup. Use when user wants to install dependencies, authenticate WhatsApp, register their main channel, or start the background services. Triggers on "setup", "install", "configure omniclaw", or first-time setup requests.
Add Graphite CLI to OmniClaw container and configure authentication. Installs Graphite for stacked PRs workflow and handles pre-authorization.
Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.
X (Twitter) integration for OmniClaw. Post tweets, like, reply, retweet, and quote. Use for setup, testing, or troubleshooting X functionality. Triggers on "setup x", "x integration", "twitter", "post tweet", "tweet".
SolidJS and SolidStart performance and correctness guidelines for AI agents. This skill should be used when writing, reviewing, or refactoring SolidJS/SolidStart code to ensure correct reactivity patterns and optimal performance. Triggers on tasks involving SolidJS components, signals, stores, Solid Query, SolidStart server functions, routing, or fine-grained reactivity.
Add Gmail integration to OmniClaw. Can be configured as a tool (agent reads/sends emails when triggered from WhatsApp) or as a full channel (emails can trigger the agent, schedule tasks, and receive replies). Guides through GCP OAuth setup and implements the integration.
| name | graphite |
| description | Manage stacked pull requests using Graphite CLI. Create, submit, and restack PR chains. |
Use Graphite CLI to manage stacked pull requests - a workflow for breaking large features into smaller, dependent PRs.
# Create a new branch off current
gt create -m "First PR in stack"
# Make changes, commit
git add .
git commit -m "Implement feature A"
# Create next branch in stack
gt create -m "Second PR in stack"
# Make more changes
git add .
git commit -m "Implement feature B"
# Submit all branches as PRs
gt stack submit
This creates multiple PRs where each depends on the one before it.
If you make changes to an earlier PR in the stack:
# Switch to the branch you want to update
gt checkout <branch-name>
# Make changes
git add .
git commit -m "Update"
# Restack all dependent branches
gt stack restack
# Show current stack
gt stack
# Show detailed log
gt log
# List all branches
gt branch
# Delete a branch and restack
gt branch delete <branch-name>
# Sync with remote
gt stack sync
Building a feature that needs multiple PRs:
# Start from main
gt checkout main
gt sync
# Create first PR: database changes
gt create -m "Add user preferences table"
# ... make changes ...
git commit -m "Add migrations and models"
# Create second PR: backend API
gt create -m "Add preferences API endpoints"
# ... make changes ...
git commit -m "Implement CRUD endpoints"
# Create third PR: frontend
gt create -m "Add preferences UI"
# ... make changes ...
git commit -m "Build settings page"
# Submit the entire stack
gt stack submit
This creates 3 PRs:
When #1 is merged, Graphite automatically restacks #2 and #3 on main.
gt stack frequently to visualize your workGraphite CLI is pre-authenticated in OmniClaw containers using your GitHub token. No manual auth needed.
Full docs: https://graphite.com/docs