Skill

amoa-developer-communication

Drafts constructive Markdown messages for code reviews, PR comments, issues, status updates, and conflicts using decision trees, tone checklists, and principles.

Markdown

git-workflow

npx claudepluginhub emasoft/ai-maestro-orchestrator-agent

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

Supporting Assets

SKILL.md

Similar Skills

code-review-communication

Provides frameworks like Conventional Comments for clear PR feedback, strategies for handling disagreements, and tips for constructive code reviews without defensiveness.

2 files3 tools

soft-skills

pull-request

Creates, updates descriptions, and adds comments to GitHub pull requests using file-based drafts for safety, emphasizing material impact and reviewer-friendly communication.

1 file

git

code-review-response

Guides technical responses to code review feedback: classify PR comments, verify issues, implement changes with evidence, and reply objectively. Useful for managing reviewer comments.

alfred-dev

Stats

Stars10

Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

Identify type — PR comment, issue, explanation, status, or conflict.
Review principles in references/key-principles.md
Select reference via references/decision-tree.md
Draft message following reference patterns.
Run pre-send checklist from references/tone-quick-reference.md
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
- 1. Be Specific, Not Vague
- 1. Separate Blocking from Non-Blocking
- 1. Acknowledge Good Work
- 1. 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