generate-changelog

Drafts pull request titles and changelog descriptions from branch commits into .git/PR_DRAFT.md.

1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/silentFellow/public-dotfiles --skill generate-changelog-silentfellow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-changelog
Source: https://github.com/silentFellow/public-dotfiles/tree/main/agents/skills/generate-changelog
Command: npx skills add https://github.com/silentFellow/public-dotfiles --skill generate-changelog-silentfellow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a clear pull request title and description from a branch full of commits is tedious and inconsistent. This Skill consolidates a branch's commits into a structured PR title and changelog draft, ready to paste when opening or updating a PR. ## Core Features & Use Cases - Base ref resolution: Detects an existing PR's base via gh pr view or falls back to dev/develop, always confirming with the user before proceeding. - Changelog consolidation: Merges and dedupes structured commit bodies into one unified changelog, or re-clusters themes directly from git diff <base>...HEAD when commits are unstructured. - Formatted draft output: Writes .git/PR_DRAFT.md with the title on line 1 and a ### CHANGELOG nested-bullet body, condensing content that exceeds ~40 lines. - Use Case: After finishing a feature branch with a dozen commits, run this Skill to produce a ready-to-paste PR title and description without manually re-reading every commit. ## Quick Start Draft a PR title and changelog description for my current branch against the dev base branch.

Frequently Asked Questions about generate-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a pull request description from branch commits?▼

Run this Skill on your branch: it reads commits via git log <base>...HEAD, merges structured commit bodies into one deduplicated changelog, and writes the title and description to .git/PR_DRAFT.md for pasting into the PR.

How to create a changelog when commits are unstructured or WIP?▼

When commit messages lack structured bodies, the Skill falls back to re-clustering changes directly from git diff <base>...HEAD, grouping them by theme into the same nested-bullet changelog format.

Does this Skill create or edit the pull request on GitHub?▼

No. It only drafts content into .git/PR_DRAFT.md and never runs gh pr create or gh pr edit. You review the draft and open or update the PR yourself.

Why use three dots instead of two in git log for PR diffs?▼

The triple-dot form base...HEAD uses the merge-base, so only the branch's own changes are included. Two dots would also pull in commits made to the base branch after divergence, polluting the changelog.

What happens if .git/PR_DRAFT.md already has content?▼

The Skill asks before overwriting an existing draft, since it may contain edits you were still working on. It never silently replaces prior content.