Menu
Write clear, conventional git commit messages — type(scope): summary, imperative mood, a body that explains the why.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | conventional-commits |
| description | Write clear, conventional git commit messages — type(scope): summary, imperative mood, a body that explains the why. |
Before committing code. Keeps history readable and changelog-friendly.
<type>(<optional scope>): <imperative summary, ≤72 chars>
<body: what changed and WHY, wrapped ~72 cols. Not how — the diff shows how.>
<optional footer: BREAKING CHANGE: …, Refs: #123>
feat (feature) · fix (bug) · refactor · perf · docs · test · chore · ci · build
fix: stop double-charging on retried webhooks
Stripe re-sends events on timeout; we keyed off event time, not id, so a
retry created a second charge. Key idempotency on the event id instead.
Write a blameless incident postmortem — timeline, impact, root cause, and concrete follow-ups, focused on systems not people.
Build small, secure container images — pinned base, non-root user, multi-stage builds, no secrets in layers, minimal attack surface.
Control and query Home Assistant through the connector's call_service tool — REST API patterns, common domains, how to find entities before acting.
Design predictable REST APIs — noun resources, correct status codes, pagination, consistent errors, and versioning.
Handle API keys, tokens and passwords safely — store them in the vault, reference by name, never in chat, repo, memory, or code.
Diagnose slow queries and add the right indexes — read the query plan, index for filters/joins/sorts, avoid over-indexing.