amoa-developer-communication

Developer Communication Skill

Overview

Effective communication with human developers in code reviews, issues, and status updates.

Prerequisites

Code review familiarity and access to communication channels.

Output

Markdown message with communication type, tone assessment, blocking status, and reference links.

Instructions

1. Identify type — PR comment, issue, explanation, status, or conflict.
2. Review principles in references/key-principles.md
3. Select reference via references/decision-tree.md
4. Draft message following reference patterns.
5. Run pre-send checklist from references/tone-quick-reference.md
6. Send and monitor for follow-up.

Copy this checklist and track your progress:

• Identified type and selected reference via decision tree
• Applied key principles (good intent, specific, blocking status)
• Drafted message and passed pre-send checklist
• Sent and monitoring for follow-up

Error Handling

See references/conflict-resolution.md

and references/tone-quick-reference.md

Examples

Input: PR uses unsafe string concatenation for SQL queries. Output: Non-blocking: "Consider parameterized queries — e.g. cursor.execute('SELECT * FROM users WHERE id = ?', (user_id,))."

See references/op-*.md for walkthroughs.

Resources

• reference-catalog.md
  • PR Comment Writing
  • Issue Communication
  • Technical Explanation
  • Conflict Resolution
  • Status Updates
  • Templates for Humans
• key-principles.md
  • 1. Assume Good Intent
  • 2. Be Specific, Not Vague
  • 3. Separate Blocking from Non-Blocking
  • 4. Acknowledge Good Work
  • 5. Provide Context for Your Feedback
• decision-tree.md
• tone-quick-reference.md
  • Examples of Constructive Communication
    • Example 1: Constructive Code Review Comment
    • Example 2: Acknowledging Good Work
  • Error Handling in Communication
  • Pre-Send Checklist