Keep a repository's history and release notes clean and legible — conventional commits, scannable PR descriptions, and a maintained changelog. Combine on any project where commit and release hygiene matters.
Git & GitHubgitgithubworkflow
Try it — copy this prompt into Claude Code
Run `npx @spectre-apps/skills recipe clean-git-workflow` to install the skills, then set this repository up for a clean git workflow: rewrite my staged changes into conventional commits, draft a scannable PR description for this branch, and create or update the changelog.
One paste installs the skills and kicks off the whole build.
Maintain a Keep a Changelog style CHANGELOG.md. Trigger when a change ships or the user asks to update the changelog.
How it fits together
Clean Git Workflow
A small bundle that makes a repo's history tell a clear story — from each commit
through the PR to the changelog.
Order
conventional-commits — format every commit as <type>(<scope>): <summary> so history is parseable and releases can be derived from it.
pr-description — turn a diff into a scannable What / Why / How / Testing writeup that leads with the user-visible effect.
changelog-keeper — roll the accepted changes into a Keep a Changelog CHANGELOG.md, grouped Added/Changed/Fixed/Removed.
Together they give you a straight line from an individual change to a released,
documented version — no archaeology required.
Prefer to drop the files in?
Copies every skill in this recipe as one block — each section is headed with the path it belongs at (.claude/skills/<slug>/SKILL.md), so you can paste them straight into your project and reference them in your prompt.