skills.rest
kurojs
kurojsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

maintainer-voice

Draft maintainer-grade async comments with early verdicts and one next step.

2|Updated Jul 29, 2025
Search Tags:#code review#PR feedback#maintainer#issue response#Jira updates#Slack messaging#Discord announcements
One-click install
npx skills add https://github.com/kurojs/EnderDots --skill maintainer-voice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maintainer-voice
Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/maintainer-voice
Command: npx skills add https://github.com/kurojs/EnderDots --skill maintainer-voice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you write maintainer-grade async comments and messages that are direct, evidence-based, and easy for contributors to act on.

Core Features & Use Cases

  • Process-aware responses for GitHub issues and PR reviews, including approvals, request-changes, and closing messages that clearly distinguish PR from idea.
  • Channel-specific messaging for Jira, Slack, and Discord while keeping the core tone consistent and action-oriented.
  • Style guardrails that enforce compact structure, early verdicts, embedded evidence in prose, and the “one next step” rule to avoid ambiguity.

Quick Start

Use the maintainer-voice skill to draft a PR review response for the attached thread, based on the intent keywords like approve, request changes, or close.

Frequently Asked Questions about maintainer-voice

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

FAQPage Schema
How do I write a PR review comment that is clear and contributor-friendly?▼

Maintainer-grade async communication requires a compact structure with an early verdict, embedded evidence in prose, and one unambiguous next step to ensure contributor-friendly PR feedback.

What is the best way to format GitHub issue responses for async collaboration?▼

The best way to format GitHub issue responses is to distinguish the PR from the idea, state an early verdict, provide embedded rationale, and end with a single unambiguous next step for the contributor.

Can I use the same direct communication style for Slack, Discord, and Jira updates?▼

Yes, you can apply a consistent, action-oriented tone across Slack, Discord, and Jira updates while adapting the messaging to each channel to maintain clear decisions and contributor-friendly next actions.

How do I draft a GitHub PR closure notice that explains the decision clearly?▼

Draft a GitHub PR closure notice by stating an early verdict, embedding evidence-based rationale directly in the prose, and providing a single unambiguous next step to explain the process decision clearly.

Why do my maintainer comments cause confusion instead of actionable feedback?▼

Maintainer comments cause confusion when they lack a compact structure, omit an early verdict, or fail to provide a single unambiguous next step, leaving contributors without clear direction on what to do next.

Related Skills

Explore More Content & Communication Skills→
unblockedunblocked
13

enrich-ticket

Enrich issue tracker tickets with organizational context and cited findings.

Official
Advanced
thananonthananon
3.1k

management-talk

Rewrite engineering updates into executive summaries for JIRA, Slack, or email.

Community
Intermediate
randalmurphalrandalmurphal

code-review-patterns

Generate structured code review feedback with evidence and severity guidelines.

Community
Basic
anysiteioanysiteio
19

anysite-vc-analyst

Analyze investor profiles, score matches, and generate personalized outreach messages.

Official
Advanced