SkillCurated by metahubEval warningsprompts

pr-summarizer

Name: pr-summarizer
Author: oxbshw

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 3 months ago

7/11Verified publisherCurated by MetaHubActively maintainedLicensedDocumentedStructuredClean repo

Ask your AI client: “install skills/pr-summarizer”.

Requires the metahub MCP server installed in your client. Set up MCP.

mh install skills/pr-summarizer

metahub 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.

Claim this repo

Stars

533

Last commit

3 months ago

7f8ee3c

Latest release

published

3 months ago

#ai
#ai-agent
#ai-agents
#fine-tuning
#finetuning-llms
#freamework
#llm
#llmops
#local-development
#mcp-server
#memory
#rag
#rag-chatbot
#voice-agent

Evaluation report

WarningsView full report

Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.7f8ee3c· 3 months ago

Documentation

4 passed1 warning

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.
Description 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)
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking

Release history

releasecurrent7f8ee3cwarn3 months ago

View on GitHub

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 --stat and git log <base>..HEAD --oneline to see scope
git diff <base>...HEAD for 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