git-commit-bullets
Git Commit with Bullet-List Body
Make commits that are easy to review and safe to ship: only intended changes are included, commits are logically scoped (split when needed), and commit messages describe what changed and why. The message body must be written as a bullet list, not a paragraph.
Inputs to ask for (if missing)
- Single commit or multiple commits? (If unsure: default to multiple small commits when there are unrelated changes.)
- Commit style: Conventional Commits are required.
- Any rules: max subject length, required scopes.
Workflow (checklist)
More from bowentan/super-agent
gitlab-mr-review
Review a GitLab merge request: fetch MR (default repo = project name), analyze the diff, and optionally post review comments. Use when asked to review an MR, do a code review on GitLab, or when the user wants MR feedback. Triggers on: review MR, review merge request, review this MR, code review GitLab, glab mr review.
27update-mr-desc
Updates merge request descriptions in GitLab by summarizing MR changes into a bulleted list, excluding changes under docs/. Use when updating an MR description via glab MCP or glab CLI, or when the user asks to summarize MR changes for the description.
5prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
4