agentleFS
sushi-killersushi-killer/sushiAI/.agents/skills/ship-pr/SKILL.md

ship-pr

Skill2 starsChanged 26 days agoMITView on GitHub

Opens a sushiAI pull request the way the release pipeline expects: <type>/<slug> branch paired with a conventional-commit title, a docs/releases/unreleased/ fragment when user-visible, npm run ci green first. Use whenever a change is ready to leave the working branch ("ship this", "open a PR", "push this up"). Never merges.

  • Commits and pushes

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ideate, review-pr and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    ideate

    Generate image-based alternatives, remixes, or new design directions from a Product Design brief. Use when the user asks for design variants, visual exploration, remixes, or image-generated approaches from provided context.

    Also in 4 projects that use this

  • DockerSkill

    review-pr

    Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

    Also in 4 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 4 projects that use this

  • GoogleSkill

    diagnosing-bugs

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

    Also in 3 projects that use this

  • GoogleSkill

    domain-modeling

    Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 3 projects that use this

  • +3 more from google

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Run npm run ci locally first: Don't open the PR to find out CI is red.

    line 28
  2. Very specific:

    Use the repo's PR template body (.github/PULL_REQUEST_TEMPLATE.md).

    line 37

“Common” is measured: kept by at least 6 in 10 of the 30 edited versions of this file we could read. “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 a PR

sushiAI merges are squash-only: the PR title becomes the literal commit message on main, and scripts/release.mjs reads that history to compute the next version. A wrong branch prefix or title breaks that pipeline silently, so this is a checklist, not a suggestion.

Steps

  1. Branch from fresh main, named <type>/<slug>:
    • feature/<slug> for a feat: change
    • fix/<slug> for a fix: change
    • chore/<slug> for anything else (docs, refactor, test, ci, perf, chore)
    • (release/<slug> is reserved for scripts/release.mjs - never use it for a normal change.)
  2. If the change is user-visible, add a fragment at docs/releases/unreleased/<slug>.md describing it in the same voice as past entries under docs/releases/ - what changed, why it matters, not an implementation diary. Skip this for pure internal/dev-only changes.
  3. Run npm run ci locally first. Don't open the PR to find out CI is red; that costs a round trip everyone else can see.
  4. Open the PR with gh pr create, using a conventional-commit title that agrees with the branch prefix (feature/ -> feat: , fix/ -> fix: , chore/ -> any other type). scripts/check-conventions.mjs enforces this pairing in CI - a mismatch fails the conventions job. A breaking change needs a ! in the title (feat!: ) AND a docs/releases/unreleased/*.md fragment, or the same check fails it. Use the repo's PR template body (.github/PULL_REQUEST_TEMPLATE.md).
  5. Watch CI: gh pr checks --watch. Report pass/fail back with the check names, not just "done."
  6. Never merge it. Merging is the owner's call, always - this skill's job ends at "ready to merge," not "merged."

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.