agentleFS
Sign inStart free
ulises-jeremiasulises-jeremias/agent-toolkit/skills/core/pr-fallback/SKILL.md

pr-fallback

Skill19 starsChanged 2 months agoMITView on GitHub

WHAT — When the repo has no GitHub PR template, structure the pull-request body using the

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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 output-handshake: user confirms where the final description will live (e.g.

    line 18
  2. Distinctive:

    If the repository adds a template later, prefer the repo over this file.

    line 19
  3. Very specific:

    If there is no .gitlab/merge_request_templates/, you may use the same Markdown structure in the merge request description for consistency, …

    line 24
  4. Distinctive:

    Do not assume a PR is always in a specific ticket system.

    line 28

≈ “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

PR body — default when no repo template (WHAT)

When to use

  • Remote is GitHub and assistant (or a file search) shows no PULL_REQUEST_TEMPLATE / pull_request_template under .github/.
  • You need a reasonable default for gh pr create --body-file until the repo adds its own template.

Instructions

  1. Run output-handshake: user confirms where the final description will live (e.g. body.md for gh, paste-only) and that a human will review.
  2. If the repository adds a template later, prefer the repo over this file.
  3. Copy sections from references/pr-body-default.md, fill placeholders (issue id, test notes), and pass the path to github-cli-workflow.

GitLab

If there is no .gitlab/merge_request_templates/, you may use the same Markdown structure in the merge request description for consistency, subject to the user’s destination choice (MR description field, file, etc.) and output-handshake.

What not to do

  • Do not assume a PR is always in a specific ticket system; the file the user points to is wherever they said in the handshake.

References

  • references/pr-body-default.md — local copy of the default body
  • development-workflow — default PR validation and DoD expectations
  • github-cli-workflow — draft PR creation
  • gitlab-cli-workflow — GitLab MRs

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.

Reviews can't be read right now.

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