agentleFS
anza-xyzanza-xyz/kit/.agents/skills/shipping-graphite/SKILL.md

shipping-graphite

Skill703 starsChanged 9 months agoMITView on GitHub

Shipping workflow using Graphite CLI. Provides guidance for committing, branching, and creating PRs with Graphite's single-commit-per-branch model.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. lorisleiva/skills★ 1100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 7 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NEVER commit, push, create branches, or create PRs without explicit user approval.

    line 12
  2. Distinctive:

    Before any git operation that creates or modifies a commit, present a review block containing: changeset content (if applicable), commit …

    line 13
  3. Very specific:

    Use gt create -am "Title" -m "Description body" for new PRs.

    line 15
  4. Very specific:

    Use gt modify -a to amend the current branch with follow-up changes (NEVER create additional commits on the same branch).

    line 16
  5. Very specific:

    ALWAYS escape backticks in commit messages with backslashes for shell compatibility (e.g.

    line 17
  6. Distinctive:

    Write commit and PR descriptions as natural flowing prose.

    line 18
  7. Very specific:

    Use gt create to create a new branch with a single commit:

    line 24
  8. Distinctive:

    Write the body as a concise flowing summary.

    line 32
  9. Very specific:

    If a .github/PULL_REQUEST_TEMPLATE.md exists, use it as a guide for structuring the PR description.

    line 33
  10. Distinctive:

    When making follow-up changes to the current branch, ALWAYS amend rather than creating new commits:

    line 37
  11. Very specific:

    Do NOT run gt submit (or gt ss) after creating or modifying branches.

    line 47
  12. Very specific:

    Only after a clean sync, run gt submit to create or update PRs for all branches in the current stack.

    line 51
  13. Distinctive:

    When commit titles or descriptions contain backticks (e.g.

    line 55
  14. Distinctive:

    Before any git operation, present this review block and wait for approval:

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ship Code Using Graphite

Guidance for shipping code using the Graphite CLI (gt). This skill teaches the agent how to create commits, branches, and PRs using Graphite's single-commit-per-branch model.

Key Rules

  • NEVER commit, push, create branches, or create PRs without explicit user approval.
  • Before any git operation that creates or modifies a commit, present a review block containing: changeset content (if applicable), commit title, and commit/PR description. ALWAYS wait for approval.
  • Show the proposed changeset entry for review before writing the changeset file.
  • Use gt create -am "Title" -m "Description body" for new PRs. The first -m sets the commit title; the second sets the PR description.
  • Use gt modify -a to amend the current branch with follow-up changes (NEVER create additional commits on the same branch).
  • ALWAYS escape backticks in commit messages with backslashes for shell compatibility (e.g. "Update \my-package` config"`).
  • Write commit and PR descriptions as natural flowing prose. Do NOT insert hard line breaks mid-paragraph.

Guidelines

Creating a New PR

Use gt create to create a new branch with a single commit:

gt create -am "Commit title" -m "Description body explaining what changed and why."
  • The first -m flag sets the commit title (first line of the commit message).
  • The second -m flag sets the commit body, which Graphite uses as the PR description when the stack is submitted.
  • Write the body as a concise flowing summary. Avoid excessive blank lines.
  • If a .github/PULL_REQUEST_TEMPLATE.md exists, use it as a guide for structuring the PR description. Fill in sections that are relevant and omit sections that don't apply (e.g. don't add "Fixes #" if there's no related issue).

Amending an Existing PR

When making follow-up changes to the current branch, ALWAYS amend rather than creating new commits:

gt modify -a

This amends the single commit on the current branch. Since Graphite uses a one-commit-per-branch model, ALWAYS use gt modify -a for follow-up changes on the same PR.

Submitting PRs

Do NOT run gt submit (or gt ss) after creating or modifying branches. The gt create and gt modify steps are the end of the workflow unless the user explicitly asks to submit or push.

When the user asks to submit, first run gt sync to ensure the local stack is up-to-date. This will restack branches from the main branch and prompt to delete any stale (merged) branches. If gt sync encounters any issues or conflicts, stop immediately and report the problem to the user before proceeding — await their instructions on how to resolve it.

Only after a clean sync, run gt submit to create or update PRs for all branches in the current stack.

Shell Escaping

When commit titles or descriptions contain backticks (e.g. for package names or code references), escape them with a backslash so the shell passes them through literally:

gt create -am "Align \`kit-plugins\` infrastructure" -m "This PR updates the shared config."

Review Block Format

Before any git operation, present this review block and wait for approval:

  1. Changeset entry (if applicable) — the proposed changelog entry and bump type.
  2. Commit title — a concise title for the commit.
  3. Commit/PR description — a short description that explains what changed and why.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.