mohitagw15856/pm-claude-skills / examples/promoter/drafted-skill
release-notes-from-git-log
VerifiedTurn a git log into user-facing release notes grouped by feature and fix. Use when asked for release notes from this git log, a changelog entry from these commits, or to turn commits into release notes. Produces a grouped changelog with one line per change and a short headline.
Release Notes From Git Log
Commits are written for the people who made them; release notes are read by the people who did not. This skill turns the log into notes a user can act on: grouped, short, in plain language, with internal noise removed.
What This Skill Produces
- A headline line for the release
- Changes grouped under Features, Fixes, and Changes, one line each, user-facing
- A migration note when anything needs action
Required Inputs
Ask for these if not provided:
- The git log (or the commit list) since the last tag
- The version or tag name
- The audience: end users, developers, or both
Framework: Group, Translate, Cut
- Group by kind from the commit prefix or message: feat, fix, chore.
- Translate each line from what changed to what the reader gains.
- Cut chores, refactors and merges unless they change behaviour.
Output Format
v:
Features
- ... Fixes
- ... Changes
- ... Migration: <none, or the one step>
Worked Examples
Example 1: a small web app release
Input (abridged): 12 commits, three prefixed feat, six fix, three chore. Output (abridged): a headline, three feature lines, six fix lines, no chores, migration: none.
Example 2: a library with a breaking change
Input (abridged): a commit renaming a public function. Output (abridged): the rename under Changes with the old and new name, and a one-line migration step.
Example 3: a hotfix
Input (abridged): one fix commit. Output (abridged): a single-line note with the headline "hotfix" and the fix.
Quality Checks
- Every line says what the reader gains, not what the code did
- Chores and merges are gone unless they change behaviour
- Grouped, one line per change, short
- A migration note exists whenever something needs action
Anti-Patterns
- Pasting commit messages. They are not notes.
- Listing every commit. Cut the noise.
- Internal tone. Ticket numbers and branch names do not belong.
Example Trigger Phrases
- "Release notes from this git log."
- "Write the changelog entry from these commits."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 197k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |