skills.rest
furkankoykiran
furkankoykiranCOMMUNITY
Explore all skills by this author →
Website𝕏@furkankoykiranGitHub

github-comment

Generate GitHub comments referencing conversation context and thread tone.

4|1|Updated Apr 26, 2026
Search Tags:#github#open-source#pull-request#issue-comment#tone-matching#comment-writing#authentic-comments
One-click install
npx skills add https://github.com/furkankoykiran/.claude --skill github-comment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-comment
Source: https://github.com/furkankoykiran/.claude/tree/main/skills/github-comment
Command: npx skills add https://github.com/furkankoykiran/.claude --skill github-comment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generic, bot-like GitHub comments fail to resonate with open source community members, come off as inauthentic, and often ignore specific context from issue or pull request discussion threads, reducing engagement and trust.

Core Features & Use Cases

  • Context-Aware Comment Drafting: Analyzes full issue/PR conversation history to pick up tone, inside jokes, timeline, and recurring callback moments to reference in comments.
  • Tone Calibration: Adjusts comment tone to match the thread, whether it's an old unresolved issue, a frustrated user thread, a technical deep-dive, or a first-time contributor's PR.
  • Use Case: Open source maintainers and contributors can use this skill to post PR descriptions, issue comments, and review replies that feel genuinely human, avoiding generic corporate phrasing and bot-like filler.

Quick Start

Use the github-comment skill to draft a context-aware reply to open issue #22194 that references the serialization bug discussed in the August comment thread and matches the frustrated tone of the original reporter.

Frequently Asked Questions about github-comment

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

FAQPage Schema
How do I write GitHub pull request comments that don't sound like a bot?▼

To write GitHub pull request comments that don't sound like a bot, you must analyze the conversation history and match the thread's tone. This approach avoids generic phrasing by incorporating specific context and callback moments from the discussion.

What is the best way to reply to frustrated users in GitHub issue threads?▼

Replying to frustrated users in GitHub issue threads requires tone calibration to match the sentiment of the original reporter. By referencing specific technical context from previous comments, your issue comments feel genuinely personal rather than dismissive.

How do I draft a PR description for first-time open source contributors?▼

Drafting a PR description for first-time open source contributors involves adjusting your tone to be welcoming while avoiding overly casual filler language. The comment should reference specific details from their contribution history to feel authentic.

Can I use context-aware comment drafting for unresolved GitHub issues?▼

Context-aware comment drafting works for unresolved GitHub issues by analyzing the full timeline and recurring callback moments. This ensures your review replies acknowledge the historical context of the thread rather than ignoring past discussion.

Why do generic bot comments fail in open source community discussions?▼

Generic bot comments fail in open source community discussions because they ignore specific context from issue or pull request threads, reducing engagement and trust. Authentic comments require referencing conversation history and matching the thread's tone to resonate with maintainers.

Related Skills

Explore More Software Engineering Skills→
sushichan044sushichan044
2

gh-timeline

Fetch GitHub issue or pull request timeline events as JSON.

Community
Basic
takemi-ohamatakemi-ohama

resolve-pr-comments

Automates replying to and resolving completed PR comment threads via GitHub CLI/APIs without changing code.

Community
Intermediate
Community-AccessCommunity-Access
387

Contributions Hub

Manage GitHub Discussions and audit community health files via the GitHub API.

Official
Advanced
Luney-IndustriesLuney-Industries
4

address-pr-comments

Categorize GitHub pull request comments and generate action plans.

Official
Advanced