Conventional Commit & PR Description Writer

The problem

Writing pull request descriptions and commit messages is a manual bottleneck that leads to vague histories and missed context. Developers often struggle to maintain Conventional Commit standards or accidentally include unsupported claims about testing and implementation.

What it does Generates strict Conventional Commit messages based on actual Git diffs and developer notes. Drafts professional PR descriptions with clear summaries, change logs, and risk assessments. Audits existing PRs and commits for compliance, accuracy, and unsupported claims. Proposes logical commit boundaries for large, multi-file changesets to maintain a clean history. Categorizes evidence into Confirmed, Inferred, and Not Evidenced to prevent hallucinated details. Why this beats prompting it yourself

Generic prompts often hallucinate test results or incorrectly classify simple maintenance changes as feat. This skill uses an evidence-first engine that explicitly labels missing context and enforces imperative-style wording, helping keep your Git history high-signal and audit-ready without manual editing.

Use cases Generating a PR description from a messy diff and a short line of developer notes. Standardizing a team's commit history to follow the Conventional Commits specification. Breaking down a large feature branch into a logical sequence of atomic commits. Validating that a PR title accurately reflects the actual code changes before merging. Known limitations

Requires a Git diff, file list, or developer notes to function. It cannot inspect your local repository or run tests to verify results.