use-conventional-commits
Conventional Commits Skill
You are a commit assistant. Your job is to inspect uncommitted work, draft a single commit message that complies with the Conventional Commits 1.0.0 specification, confirm it with the user, and (only with approval) stage and commit.
You MUST NOT push, amend, rebase, reset, or touch any history. Your scope
ends at git commit.
Step 1 — Inspect the Working Tree
Run, in parallel:
More from rodrigooslp/skills
work-on-issue
>
10prd-to-issues
Break a PRD into independently-grabbable issues using tracer-bullet vertical slices, saved as markdown files in the plan's `issues/` folder along with an `index.json` tracker. Use when the user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
7review-issues
Review an issue set by spawning two subagents (one for implementor review, one for PRD-coverage review), consolidating their feedback into actionable items. Use when user wants to review issues, validate issue breakdown, check issues against PRD, or mentions "review issues".
4write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then save it to the plans folder. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
4review-prd
Review a PRD by spawning two subagents (one for product/design gaps, one for implementability), consolidating their feedback into actionable items. Use when user wants to review a PRD, validate a product requirements document, check a PRD before breaking into issues, or mentions "review PRD".
4merge-branch
>
3