agentleFS
Martin-HausleitnerMartin-Hausleitner/martins-awesome-skills/skills/github/github-pr-workflow/SKILL.md

github-pr-workflow

Skill3 starsChanged 6 months agoMITView on GitHub

Use when creating, updating, reviewing, testing, or merging a GitHub pull request

  • Commits and pushes

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use github-repo-management, minecraft-modpack-server and 4 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.
  • math-incSkill

    github-repo-management

    Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.

    Also in 5 projects that use this

  • math-incSkill

    minecraft-modpack-server

    Set up a modded Minecraft server from a CurseForge/Modrinth server pack zip. Covers NeoForge/Forge install, Java version, JVM tuning, firewall, LAN config, backups, and launch scripts.

    Also in 3 projects that use this

  • +4 more from math-inc

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep pull request work reviewable: one branch, one purpose, clear tests, and a concise body.

    line 10
  2. Distinctive:

    Create a branch with a conventional prefix:

    line 21
  3. Distinctive:

    Commit with a precise message:

    line 35
  4. Distinctive:

    Do not include private config, real credentials, private logs, or local cache files.

    line 59
  5. Distinctive:

    Run the repo safety audit before opening public PRs.

    line 60

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

GitHub PR Workflow

Overview

Keep pull request work reviewable: one branch, one purpose, clear tests, and a concise body.

Workflow

  1. Inspect status:
git status --short --branch
git remote -v
  1. Create a branch with a conventional prefix:
git checkout -b codex/short-description
  1. Make scoped changes and run relevant tests.
  2. Stage only intended files:
git add README.md docs/SKILL_CATALOG.md
git diff --cached --stat
  1. Commit with a precise message:
git commit -m "docs: improve public skill catalog"
  1. Push and open the PR:
git push -u origin HEAD
gh pr create --fill

PR Body

Include:

  • Summary
  • Verification
  • Risk or rollback notes
  • Screenshots for visible docs/site changes when useful

Safety

  • Do not include private config, real credentials, private logs, or local cache files.
  • Run the repo safety audit before opening public PRs.

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.