pr-summarizer
Use when opening a PR — produces a clean PR description (what / why / how to verify / risks) from a branch diff against base.
pinned to #7f8ee3cupdated 2 weeks ago
Ask your AI client: “install skills/pr-summarizer”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/pr-summarizermetahub onboarded this repo on the author's behalf.
If you own github.com/oxbshw/LLM-Agents-Ecosystem-Handbook on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
533
Last commit
2 weeks ago
Latest release
published
- #ai
- #ai-agent
- #ai-agents
- #fine-tuning
- #finetuning-llms
- #freamework
- #llm
- #llmops
- #local-development
- #mcp-server
- #memory
- #rag
- #rag-chatbot
- #voice-agent
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.7f8ee3c· 2 weeks ago
Documentation
41Description quality
26 words · 125 chars — "Use when opening a PR — produces a clean PR description (what / why / how to ver…"
README is present and substantial
19,199 chars · 20 sections · 2 code blocks
Tags / topics declared
14 total — ai, ai-agent, ai-agents, fine-tuning, finetuning-llms, freamework (+8)
README has usage / example sectionswarn
README has no Usage / Example / Quick start / Installation heading at any level
Add a `# Usage`, `## Quick start`, or similar section so end users can copy/paste a working invocation. Code blocks alone work too if there are several.
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrent7f8ee3cwarn2 weeks ago
Contents
When to use
- Just before opening a PR
- After force-pushing a substantive update to an existing PR (refresh description)
When NOT to use
- Drafts the user is still iterating on (the summary will go stale immediately)
- Massive diffs (> 1000 lines) — ask the user to scope first
Inputs
| Name | Type | Required | Notes |
|---|---|---|---|
base | string | no | default origin/main |
branch | string | no | default current HEAD |
Outputs
A markdown PR body with sections: Summary, Why, How tested, Risks, Linked.
Workflow
git diff <base>...HEAD --statandgit log <base>..HEAD --onelineto see scopegit diff <base>...HEADfor content- Group changes by area (one bullet per logical concern, not per file)
- Pull "why" from commit messages + linked tickets if mentioned
- Identify test artifacts touched; surface as How tested (or flag if none)
- Risks: any High-risk paths touched? auth, billing, migrations? mention.
- Linked: parse
Fixes #/Refs #from commits
References
Success criteria
- Description ≤ 25 lines
- Every "why" claim is supported by a commit message or visible in the diff
- Risks section honest about unknowns ("untested in production data shape")
Failure modes
- No commit messages worth quoting → "Why" sourced from diff only; flag this
- Diff touches secrets /
.env*→ STOP and surface; PR shouldn't include them
Reviews
No reviews yet. Be the first.
Related
Browser Use
🌐 Make websites accessible for AI agents. Automate tasks online with ease.
Gpt Researcher
An autonomous agent that conducts deep research on any data using any LLM providers
Guizang Ppt Skill
AI-agent Skill for generating polished HTML slide decks: editorial magazine and Swiss layouts, image prompts, social covers, and a WebGL/low-power presentation runtime.
mh install skills/pr-summarizer