agentleFS
theraihanrakibbtheraihanrakibb/agent-skills/pr-draft/SKILL.md

pr-draft

Skill0 starsChanged 3 days agoMITView on GitHub

Generates a clean Conventional Commit message, PR description, and changelog entry from staged or recent git changes when the user asks "write a commit message", "draft a PR", "what should my commit message be", "summarize my diff", or "make a PR description". Use this skill whenever the user wants to turn git changes into well-structured commit/PR text.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Get the diff: Run bash scripts/git-diff-staged.sh from the plugin root to fetch the staged diff.

    line 16
  2. Distinctive:

    Don't push without explicit confirmation.

    line 24
  3. Distinctive:

    Don't amend published commits.

    line 25

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

Clean Commit / PR Writer

When to Use

  • User asks for a commit message, PR description, or changelog entry.
  • User has staged changes and wants to summarize them.
  • User is about to push and wants a clean message.

How to Use

  1. Get the diff. Run bash scripts/git-diff-staged.sh from the plugin root to fetch the staged diff. If nothing is staged, fall back to git diff HEAD~1 (last commit) or ask the user what to base the message on.
  2. Generate three outputs:
    1. Conventional Commit message — <type>(<scope>): <subject> then a body. Types: feat, fix, docs, style, refactor, perf, test, chore, build, ci. Subject ≤ 72 chars, imperative mood, lowercase first word, no period.
    2. PR description — use templates/pr-description.md. Sections: Summary, Changes (bulleted), Why, Testing, Screenshots (placeholder).
    3. Changelog entry — one-line Keep a Changelog style entry under the right section (Added / Changed / Fixed / Removed).
  3. Present the message to the user. If they approve, you may run git commit -m "<message>" for them — but only after explicit confirmation.

Rules

  • Don't push without explicit confirmation.
  • Don't amend published commits.

References

  • templates/pr-description.md
  • scripts/git-diff-staged.sh
  • hooks/validate-commit.sh (the enforcing hook)

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.