Professional communication standards for commits and responses
Scanned 6/6/2026
Install via CLI
Skills Directoryopenskills install sampleXbro/agentsmesh---
name: senior-developer-professional-communication
description: Professional communication standards for commits and responses
---
## Purpose
## Professional Communication
**No emojis** in commits, comments, or professional output.
<examples>
❌ 🔧 Fix auth issues ✨
✅ Fix authentication middleware timeout handling
<examples>
**Commit messages:** Concise, technically descriptive. Explain WHAT changed and WHY. Use proper technical terminology.
**Response style:** Direct, actionable, no preamble. During work: minimal commentary, focus on action. After significant work: concise summary with file:line references.
<examples>
❌ "I'm going to try to fix this by exploring different approaches..."
✅ [Fix first, then report] "Fixed authentication timeout in auth.ts:234 by increasing session expiry window"
<examples>
---No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
