agentleFS
Sign inStart free
anza-xyzanza-xyz/kit/.agents/skills/shipping-git/SKILL.md

shipping-git

Skill702 starsChanged 9 months agoMITView on GitHub

Shipping workflow using standard Git and GitHub CLI. Provides guidance for committing, branching, and creating PRs.

  • Commits and pushes

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

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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. Distinctive:

    Use standard git add and git commit workflows.

    line 15
  4. Very specific:

    Use gh pr create for pull requests.

    line 16
  5. Distinctive:

    Write commit and PR descriptions as natural flowing prose.

    line 17
  6. Distinctive:

    Follow conventional commit message format:

    line 23
  7. Distinctive:

    Use present tense, imperative mood (e.g.

    line 32
  8. Distinctive:

    Create a descriptive branch name before committing:

    line 36
  9. Distinctive:

    Use the GitHub CLI to create PRs:

    line 46
  10. Very specific:

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

    line 52
  11. Distinctive:

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

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Git

Guidance for shipping code using standard Git and the GitHub CLI (gh). This skill teaches the agent how to create commits, branches, and pull requests following conventional workflows.

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 standard git add and git commit workflows. Concise title on the first line, blank line, then description body.
  • Use gh pr create for pull requests.
  • Write commit and PR descriptions as natural flowing prose. Do NOT insert hard line breaks mid-paragraph.

Guidelines

Creating Commits

Follow conventional commit message format:

git add -A
git commit -m "Commit title" -m "Description body explaining what changed and why."
  • The first -m sets the commit title (first line). Keep it concise and descriptive.
  • The second -m sets the commit body. Explain what changed and why.
  • Use present tense, imperative mood (e.g. "Add feature" not "Added feature").

Creating Branches

Create a descriptive branch name before committing:

git checkout -b feature/short-description

Common prefixes: feature/, fix/, refactor/, docs/, chore/.

Creating Pull Requests

Use the GitHub CLI to create PRs:

gh pr create --title "PR title" --body "Description explaining what changed and why."
  • 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).

Pushing Changes

Push the branch and set the upstream:

git push -u origin HEAD

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.

Check your setup, free