name	Commit Helper
description	Write clear, conventional git commit messages and summarize a set of changes.
when_to_use	When the user asks for a commit message, wants to summarize a diff, or is preparing to commit code.

Commit Helper

Help the user produce high-quality git commit messages.

Guidelines

Follow Conventional Commits: type(scope): subject.
- Common types: feat, fix, refactor, docs, chore, test, perf, build.
Keep the subject in the imperative mood, ≤ 72 characters, no trailing period.
Add a body only when it adds value: explain the why, not the what.
Group unrelated changes into separate commits and suggest the split.

Output

When asked for a commit message, return just the message (subject + optional body), ready to paste. When summarizing a diff, list the notable changes grouped by area.

Más de este repositorio

mismo repositorio

dome-reproduce-ui

maxprain12/dome

Reproducir bugs de UI con Electron + worktree aislado (DOME_PROFILE) y DevTools; plantilla de plan.

2026-07-1823

observability-dome

maxprain12/dome

Consultar señal local (OTLP/Vector) cuando el stack de docs/observability está levantado; plantillas de preguntas para agentes.

2026-07-1823

email-triage

maxprain12/dome

Prioritize inbox work, VIP follow-ups, and reminder SLAs using email domain memory.

2026-07-1823

social-growth

maxprain12/dome

Advise on social content strategy, SEO discovery, tone, and growth KPIs using domain memory.

2026-07-1823

source-synthesizer

maxprain12/dome

Synthesize multiple sources into grounded, well-cited summaries and claims.

2026-06-2123

study-planner

maxprain12/dome

Turn resources and goals into a concrete, spaced study plan and flashcard suggestions.

2026-06-2123

name	Commit Helper
description	Write clear, conventional git commit messages and summarize a set of changes.
when_to_use	When the user asks for a commit message, wants to summarize a diff, or is preparing to commit code.

Commit Helper

Help the user produce high-quality git commit messages.

Guidelines

Follow Conventional Commits: type(scope): subject.
- Common types: feat, fix, refactor, docs, chore, test, perf, build.
Keep the subject in the imperative mood, ≤ 72 characters, no trailing period.
Add a body only when it adds value: explain the why, not the what.
Group unrelated changes into separate commits and suggest the split.

Output

When asked for a commit message, return just the message (subject + optional body), ready to paste. When summarizing a diff, list the notable changes grouped by area.