skills.rest
EpicenterHQ
EpicenterHQOFFICIAL
Explore all skills by this author →
Website𝕏@EpicenterHQGitHub

github-issues

Enforce consistent GitHub issue and PR comment guidelines for community interaction.

4.7k|374|Updated Mar 16, 2023
Search Tags:#tone#github#communication#issues#guidelines#pull-requests
One-click install
npx skills add https://github.com/EpicenterHQ/epicenter --skill github-issues-epicenterhq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/github-issues
Command: npx skills add https://github.com/EpicenterHQ/epicenter --skill github-issues-epicenterhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub project teams need consistent, respectful communication on issues and pull requests. This Skill provides standardized patterns to respond to bugs, feature requests, and discussions, reducing friction and confusion.

Core Features & Use Cases

  • Acknowledgment and empathy prompts for issues and PRs.
  • Opening patterns and anti-pattern avoidance to maintain tone.
  • Reference to writing-voice guidelines for tone consistency across teams.

Quick Start

Follow the GitHub issue and PR comment guidelines when engaging with new reports or discussions.

Frequently Asked Questions about github-issues

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

FAQPage Schema
What are GitHub issue commenting guidelines for maintaining respectful community communication?▼

GitHub issue commenting guidelines define required structure and tone for community interaction by detailing acknowledgment, debugging, and follow-up patterns to maintain consistent, respectful communication across issues and pull requests.

How do I respond to GitHub bug reports and feature requests constructively?▼

Respond to GitHub bug reports and feature requests using standardized acknowledgment and empathy prompts, applying opening patterns and avoiding anti-patterns to reduce friction and confusion in community discussions.

What tone should I use when commenting on GitHub pull requests?▼

Tone for GitHub pull request comments is enforced through writing-voice guidelines that define opening, acknowledgment, and debugging patterns, ensuring consistent and helpful communication across team interactions.

Does this Skill apply to all types of GitHub discussions and issue reports?▼

This Skill applies to responding to GitHub issues, bug reports, feature requests, and discussions, providing standardized patterns to guide respectful and helpful communication across all community interaction types.

How do I avoid communication friction when handling GitHub issues in a team?▼

Avoid communication friction by following standardized GitHub issue and PR comment guidelines that enforce acknowledgment patterns, tone consistency, and structured follow-up responses for community engagement.

Related Skills

Explore More Content & Communication Skills→
MCERQUAMCERQUA
1

voice-flow

Enforce voice interaction rules for acknowledgments, tone, and interruptions.

Community
Intermediate
SocketDevSocketDev
56

driving-cursor-bugbot

Automate responses, classifications, and fixes for Cursor Bugbot review comments in GitHub pull requests.

Official
Advanced
marin-communitymarin-community
1.2k

handle-gh-scrub

Automate scheduled GitHub issue and pull request triage scrub runs.

Official
Intermediate
oborchersoborchers
28

developer-experience

Standardize project setup and automate development tasks with Makefile targets.

Community
Intermediate