agentleFS
Sign inStart free
OneByJorahOneByJorah/VirtOffice/.agents/skills/pr-workflow/SKILL.md

pr-workflow

Skill23 starsChanged 15 days agoMITView on GitHub

Branch, commit, open a pull request, and shepherd CI to green using git and the gh CLI. Use whenever agent work needs to be delivered to a repo.

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 4

    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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Start from an up-to-date default branch: git switch main && git pull --ff-only.

    line 10
  2. Very specific:

    Create a branch: git switch -c agent/<short-task-name>.

    line 11
  3. Distinctive:

    Run the project checks locally before pushing.

    line 13
  4. Distinctive:

    When green, report the PR link, check status, and anything the reviewer must look at.

    line 17
  5. Distinctive:

    Do not edit workflow files to make a failing check pass.

    line 22
  6. Distinctive:

    If the same check fails twice, stop and report what you tried.

    line 23

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

pr-workflow

Steps

  1. Start from an up-to-date default branch: git switch main && git pull --ff-only.
  2. Create a branch: git switch -c agent/<short-task-name>.
  3. Make small, logical commits with Conventional Commit messages (feat:, fix:, docs:, chore:).
  4. Run the project checks locally before pushing.
  5. Push: git push -u origin HEAD. Never push to main. Never force-push without approval.
  6. Open the PR: gh pr create --fill, then fill in what changed, why, and how it was tested.
  7. Watch CI: gh pr checks --watch. If it fails, read the logs (gh run view --log-failed), fix, push again.
  8. When green, report the PR link, check status, and anything the reviewer must look at. Do not merge unless told to.

Rules

  • One concern per PR. Split unrelated work.
  • Do not edit workflow files to make a failing check pass. Fix the cause.
  • If the same check fails twice, stop and report what you tried.

Download now (ZIP)

  • Other versions22 projects use a version of this.

    Word for word · 1

    1. OneByJorah/offivo★ 17100% same

    Edited · 0

    None found.

    Wrote their own version · 21

    1. tursodatabase/turso★ 25ksame name
    2. esphome/esphome★ 12ksame name
    3. open-edge-platform/anomalib★ 6.4ksame name
    4. Chorus-AIDLC/Chorus★ 1.2ksame name
    5. glommer/pgmicro★ 1.2ksame name
    6. Tencent-Hunyuan/UniRL★ 1ksame name
    7. esphome/esphome-docs★ 466same name
    8. notque/claude-code-toolkit★ 444same name
    9. notque/vexjoy-agent★ 444same name
    10. mezotv/notra★ 256same name

    11 more not listed

    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.

  • Used alongsideProjects with it also use workflow and code-review.

    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.
    • VercelSkill

      workflow

      Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.

      Also in 4 projects that use this

    • GoogleSkill

      code-review

      Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

      Also in 3 projects that use this

  • In this repository7 other files it gives its agents.

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