amoa-developer-communication

Compose constructive developer-facing messages for pull requests and issues.

13|Updated Mar 2, 2026

Search Tags:#templates #conflict-resolution #code-review #issue-triage #status-updates #developer-communication

Ready to run

npx skills add https://github.com/Emasoft/ai-maestro-orchestrator-agent --skill amoa-developer-communication

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: amoa-developer-communication
Source: https://github.com/Emasoft/ai-maestro-orchestrator-agent/tree/main/skills/amoa-developer-communication
Command: npx skills add https://github.com/Emasoft/ai-maestro-orchestrator-agent --skill amoa-developer-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps agents and maintainers communicate clearly and professionally with human developers to reduce misunderstanding, speed reviews, and resolve disagreements without damaging relationships.

Core Features & Use Cases

PR Review Guidance: Structured templates and tone guidelines for blocking, non-blocking, and praise comments.
Issue & Feature Responses: Acknowledgment, reproduction steps, and expectation-setting templates for bug reports and feature requests.
Conflict Resolution & Status Updates: Decision frameworks, escalation paths, and progress-update formats that clarify blockers and next steps.
Reference Library: Decision trees, example operations, and pre-send checklists to ensure messages are specific, actionable, and respectful.

Quick Start

Draft a constructive PR review comment that marks a null pointer as blocking, explains why, and proposes a safe fix with an optional non-blocking improvement suggestion.

Frequently Asked Questions about amoa-developer-communication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write a constructive PR review comment that blocks a bug without being harsh?▼

To write a constructive PR review comment, label the issue as blocking, explain the specific defect like a null pointer risk, and propose a safe actionable fix. Follow tone guidelines and use a pre-send checklist to keep the message respectful.

What is the best way to structure developer status updates for stakeholders?▼

The best way to structure developer status updates is using a progress-update format that clarifies blocking status, highlights next steps, and cites reference documents. This ensures stakeholders understand blockers and expected outcomes immediately.

How do I respond to a GitHub bug report with clear reproduction steps and expectations?▼

To respond to a GitHub bug report, use an acknowledgment template to confirm receipt, provide reproduction steps, and set expectations for issue triage. This reduces misunderstanding and speeds up the technical explanation process.

Can I use templates for conflict resolution in developer communication?▼

Yes, you can use decision frameworks and escalation path templates for conflict resolution in developer communication. These templates help resolve disagreements professionally while maintaining clear, actionable technical explanations.

How do I draft a non-blocking improvement suggestion for a pull request?▼

To draft a non-blocking improvement suggestion for a pull request, apply structured templates that separate the blocking issue from optional enhancements. Cite reference documents and pass the message through a pre-send checklist to ensure clarity.

When do I need a pre-send checklist for issue triage and technical explanations?▼

You need a pre-send checklist for issue triage and technical explanations when you want to ensure messages are specific, actionable, and respectful. It verifies that blocking status is labeled and fixes are proposed before sending.