external-comms

To draft responses for GitHub issues and discussions, this Skill scans open threads, classifies the response type, and generates template-based drafts. It verifies full-thread context and requires explicit human approval before posting any reply.

Classifying GitHub community threads for triage involves analyzing open conversations and sorting them into categories like troubleshooting, feature guidance, or acknowledgment. This process ensures each thread receives an appropriate, contextual draft response for human review.

Yes, you can automate GitHub issue triage without posting directly. The Skill prepares response drafts with confidence levels and audit-ready notes, enforcing a strict human approval checkpoint so no automated replies are published blindly.

Audit logging for GitHub discussion management records the classification, contextual review, and confidence assessment of each drafted response. This creates an audit-ready trail of the drafting process that reviewers can verify before granting final approval.

Available response templates for GitHub issue triage cover welcome, troubleshooting, feature guidance, redirect, acknowledgment, closing, technical uncertainty, empathetic disagreement, and information request. These templates help structure drafts based on the thread's classification.

You should not use automated response drafting for GitHub threads when a conversation requires immediate posting or lacks clear classification. The process mandates full-thread verification and human approval, making it unsuitable for bypassing review workflows.