Agent skill · Documentation

post-issue-comment

Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments

dyoshikawa1,265★ · +16/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add dyoshikawa/rulesync --skill post-issue-comment --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Path: .rulesync/skills/post-issue-comment/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,285 · +20 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

arguments = the user's request Parse `arguments` as: - `target_issue`: the issue number (or URL) to reply to - `intent`: the gist of the reply the user wants to post (what to say, the stance to take, the points to cover) If `target_issue` is not provided, ask the user which issue to comment on. If `intent` is not provided, ask the user what the reply should convey. ## Step 1: Gather Issue Context Run the following in parallel: - Get the issue description and metadata: `gh issue view <issue_number>` - Get the issue comments: `gh issue view <issue_number> --comments` If the issue references related pull requests, commits, or files that are needed to craft an informed reply, gather that context as well. ## Step 2: Draft the Reply Based on the issue content and the user's `intent`, draft a reply comment. - Ground the reply in the actual discussion — address the latest comment or the original issue as appropriate. - Reflect the user's `intent` faithfully; do not add positions the user did not ask for. - If relevant context is missing or a decision cannot be made without more information, say so in the reply rather than guessing. ## Step 3: Post the Comment Post the drafted reply using:

What's inside
Steps it walks through
  1. Step 1: Gather Issue Context
  2. Step 2: Draft the Reply
  3. Step 3: Post the Comment
  4. Writing Style
  5. Step 4: Report
Commands it runs
gh issue comment <issue_number> --body "<reply body>"
More from rulesync
All skills →
About this skill
What does the post-issue-comment skill do?

Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments

How do I install it?

Run `npx skills add dyoshikawa/rulesync --skill post-issue-comment --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going