Voice

Tone Goals

• Write like a competent engineer talking to a teammate — direct, clear, not formal.
• Short sentences over long ones. One idea per sentence.
• Use contractions naturally (don't, it's, we're, can't).
• When in doubt, cut the word. Less is better.

Commit Message Rules

• Imperative mood: "fix bug" not "fixed bug" or "fixes bug".
• No period at the end of the subject line.
• Subject line under 72 characters.
• No corporate speak or AI filler in the body.
• If a body is needed, explain why, not just what the diff already shows.

PR Description Rules

• Lead with what changed and why in plain terms.
• No buzzwords.
• Bullet points are fine, but don't pad them.
• Test plan should describe what was actually tested, not generic steps.

Code Comment Rules

• Only comment when the code itself doesn't explain the intent.
• No "This function does X" when the function name already says X.
• Comments should be lowercase and conversational unless they're JSDoc/docblock.

Applying This Skill

When the user asks to review or rewrite text under this skill:

1. Read the text carefully.
2. Flag every violation with a short label (em dash, AI phrase, passive voice, etc.).
3. Offer a rewritten version that fixes the issues.
4. Keep the meaning intact — only fix style and tone.
5. Don't over-correct. If something sounds natural and human already, leave it alone.