agentleFS
Sign inStart free
wataru-maedawataru-maeda/react-native-boilerplate/.agents/skills/manage-prs/SKILL.md

manage-prs

Skill521 starsChanged 15 days agoMITView on GitHub

Create, review, and merge GitHub pull requests and publish releases using repository Git rules. Use for requests to open a PR, push and create a PR, review PRs, merge a PR, or tag a release and write release notes.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Follow Git rules. Work branches target dev.

    line 8
  2. Very specific:

    Write type(scope): description, at most 70 characters.

    line 23
  3. Distinctive:

    Remove empty sections and placeholders.

    line 33
  4. Very specific:

    Never pass --subject. GitHub titles the commit <PR title> (#<N>), which links it back to the PR.

    line 39
  5. Very specific:

    Keep work branches. Delete them only when cleanup is requested.

    line 40

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

Manage PRs

Follow Git rules. Work branches target dev. Promotion PRs go from dev to stg and from stg to main.

Actions

RequestRead
Open a PR for the current branchcreate.md
Review one or more PRsreview.md
Promote dev → stg → mainpromote.md
Tag and publish a releaserelease.md

PR Rules

Title

  • Write type(scope): description, at most 70 characters. Use the types and scopes in Commits.
  • Squash merges use the title as the commit message.
  • Title promotion PRs chore: promote dev to stg or chore: release v<version> for stg to main.

Body

  • Fill .github/pull_request_template.md from the actual diff and commits. Never reuse old text.
  • Link related issues in Overview with Closes #N.
  • Tick only checks that ran. Record failures and skipped checks in Notes.
  • Fill Test Cases with actual results, including Maestro flows and the platforms they ran on. Remove the table when there are none.
  • Remove empty sections and placeholders. Leave screenshots to the user when UI changed.

Merge

  • Merge only when asked and after required checks pass.
  • Squash merge work branches into dev. Use merge commits for promotion and hotfix merge-back PRs (Merge and Version).
  • Never pass --subject. GitHub titles the commit <PR title> (#<N>), which links it back to the PR.
  • Keep work branches. Delete them only when cleanup is requested. Never delete dev, stg, or main.
gh pr checks <N> --watch
gh pr merge <N> --squash                   # work branches into dev
gh pr merge <N> --merge                    # dev → stg, stg → main, hotfix merge-back

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. BillChirico/bills-agent-skills★ 6same name

    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.

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