SkillsAdd

milistu/agent-skills

pr-message

Write a concise, high-signal GitHub pull request message that explains intent, impact, and risk

First seen Feb 11, 2026

Installation

$ npx skills add milistu/agent-skills --skill pr-message
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from milistu/agent-skills.

npx skills add milistu/agent-skills
apple-human-interface-guidelines 69 humanizer 39 conventional-comments 37 challenge-me 35 conventional-commits 28 pr-review 24 google-adk 8 commit 1

Browse all from milistu/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 8
License MIT
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,921 B
  • docs SUMMARY.md 113 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 30 installs

SKILL.md

Write PR Message

Overview

Write a concise, high-signal GitHub pull request message that explains intent, impact, and risk without duplicating information already visible in GitHub.

PR Structure

Summary

  • 1–3 sentences.
  • Explain what this PR does and why it exists.
  • Focus on behavior and outcome, not implementation details.
  • Do not list files, commits, tickets, or branches.

What Changed

  • 1–3 short bullet points.
  • Describe behavioral or functional changes only.
  • No file names or low-level implementation details.
  • Skip this section if it adds no value.

Testing

  • 1–2 bullets describing how this was verified.
  • Be concrete (tests added, manual flows checked, API exercised).
  • Avoid generic statements like "tests passed".

Screenshots (UI only, optional)

  • Include screenshots only if this PR changes UI or UX.
  • Prefer inline images over external links.
  • Omit this section entirely for non-UI changes.

Risk / Rollout

  • Answer briefly:

- Is this feature-flagged? - Is a migration required? - How can this be reverted?

  • "No / Not needed" is a valid and useful answer.

Notes for Reviewers (Optional)

  • Call out:

- Tricky logic - Non-obvious decisions - Areas that deserve extra attention

  • Keep this short and targeted.

Rules

  • Keep the entire PR message scannable.
  • Avoid repeating information GitHub already shows.
  • Prefer clarity over completeness.
  • Omit sections that don't apply rather than filling them with placeholders.
  • Always write PR message in markdown code.

Steps

  1. Review the changes and commits on the branch.
  2. Write the Summary first.
  3. Add only the sections that meaningfully help a reviewer.
  4. Output a clean PR message ready to paste into GitHub.