agentleFS
Sign inStart free
chinmay-sawantchinmay-sawant/developer-skills/skills/PR/SKILL.md

PR

Skill0 starsChanged 3 months agoMITView on GitHub

Templates and checklists for PRs, issues, and progress comments so every PR has the same shape. Use when creating a PR, issue, or progress comment.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use these templates when opening a GitHub PR, issue, or progress comment so every thread has the same shape.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 - templates for shipping

Use these templates when opening a GitHub PR, issue, or progress comment so every thread has the same shape.

Templates in this skill

  • PR_TEMPLATE.md - PR title convention, summary, changes, impact table, test plan, related issues, and gh pr create with --assignee "@me" and labels
  • ISSUE_TEMPLATE.md - context, scope, out of scope, success criteria, and gh issue create
  • COMMENT_TEMPLATE.md - factual progress updates without chatty trailing prompts

Load the relevant template file and follow it verbatim.

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.

Check your setup, free