agentleFS
connext-solutionsconnext-solutions/flowctl/.claude/skills/ship-pr/SKILL.md

ship-pr

Skill1 starsChanged 5 days agoApache-2.0View on GitHub

Use before pushing a branch or opening a pull request in flowctl. Runs the local gates, fills the PR template truthfully, sets base, labels and stack position, and gets the user's go before anything is published.

  • Commits and pushes

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ideate, triage and 7 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

  • 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

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

  • +3 more from google

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Not on main. Commits follow Conventional Commits (the commit-msg hook enforces it).

    line 10
  2. Distinctive:

    If the change touches System 1 prompts or protocol: contract tier run (billed, ask first) and the golden test diff explained.

    line 13
  3. Distinctive:

    If it touches exploration, replay or heal: a result of a trial on a real app, or say why not.

    line 14
  4. Very specific:

    Show the title and body to the user and wait for a go: before git push / gh pr create.

    line 21
  5. Very specific:

    After creating: gh pr checks <n> --watch.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 29 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 pull request

Gates (all local, before push)

  1. Not on main. Commits follow Conventional Commits (the commit-msg hook enforces it).
  2. bun run verify green (the pre-push hook runs it too).
  3. Secrets: docker run --rm -v "$PWD:/repo" zricethezav/gitleaks:v8.30.1 detect --source /repo --log-opts=origin/<base>..HEAD --redact finds nothing.
  4. If the change touches System 1 prompts or protocol: contract tier run (billed, ask first) and the golden test diff explained.
  5. If it touches exploration, replay or heal: a result of a trial on a real app, or say why not.

The PR

  1. Base: main, or the branch below it in a stack (stack skill).
  2. Body: .github/pull_request_template.md, every section filled. Tick an invariant only if you checked it. No Co-Authored-By / "Generated with".
  3. Labels: one type:*, every area:* touched, phase:* if planned work, status:stacked in a stack.
  4. Show the title and body to the user and wait for a go before git push / gh pr create.
  5. After creating: gh pr checks <n> --watch; a red CI is fixed on the branch, never by skipping a check.

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.