commit-standards

Commit message formatting standards. Use when creating commits or PRs to ensure consistent, high-level messages.

SKILL.md.claude/skills/commit-standards/SKILL.md

<TASKNUMBER|MAINT>: <short description>

- <high-level change 1>
- <high-level change 2>

First line: task number, colon, short description (under 72 chars)
Use MAINT as the prefix when the change isn't tied to a task/defect number — never invent one
Describe WHAT changed and WHY, not HOW
NO implementation details (no function names, query syntax, line counts)
NO technical specifics

See examples.md for good vs bad examples.

Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context polluti...

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration p...

This skill should be used when the user asks to "create an esphome config", "set up an esp32 device", "configure esphome...