Skip to main content
skill CX Codex

post-issue-comment — Claude Code skill: use and install

This skill reads a GitHub issue, drafts a concise English reply, and posts it. Use it when the response needs to reflect the existing discussion.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add dyoshikawa/rulesync --skill post-issue-comment -a claude-code
Open on GitHub

What post-issue-comment does

The skill takes an issue number or URL together with the point the reply should make. When either part is missing, it asks for clarification. It then fetches the issue description, metadata, and comments with gh issue view, and can inspect related pull requests, commits, or files when they matter.

It drafts a concise English comment and sends it with gh issue comment <issue_number> --body "<reply body>". The reply follows the discussion, preserves the user's position, and avoids adding claims the user did not request. Plain paragraphs are preferred over headings, horizontal rules, and long bullet lists.

The posting step depends on GitHub CLI being available in PATH. When the discussion lacks enough context for a decision, the skill says so in the reply instead of guessing.

What it helps with

  • gather a GitHub issue's description and comments
  • check the latest discussion before replying
  • turn a user's intent into an English comment
  • post the drafted reply to the issue

Example prompts for the agent

  • Read the GitHub issue I specify and post a short reply that agrees with the proposal and asks for a test.
  • Review the issue discussion, explain politely why the proposed change does not fit, and mention the related files.
  • Use my intent to draft an English reply to the issue, then publish the comment.

How to install post-issue-comment

1Skills CLI (Vercel)

npx skills add dyoshikawa/rulesync --skill post-issue-comment -a claude-code

2Manually: put the files in place

~/.claude/skills/post-issue-comment/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/post-issue-comment/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about post-issue-comment

How do I install post-issue-comment in Claude Code?

Run npx skills add dyoshikawa/rulesync --skill post-issue-comment -a claude-code, then check ~/.claude/skills/post-issue-comment/SKILL.md.

What does post-issue-comment do?

It gathers GitHub issue context, turns the user's intent into a concise English reply, and posts that reply through GitHub CLI.

What does post-issue-comment need to publish a comment?

It runs gh issue view and gh issue comment, so GitHub CLI must be available. The request also needs the target issue and the point the reply should convey.

Source text

SKILL.md · MIT
---
name: post-issue-comment
description: >-
  Post a reply comment on a GitHub issue in English with a natural, concise
  writing style, based on the intent passed as arguments
targets:
  - "*"
---

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:

```bash
gh issue comment <issue_number> --body "<reply body>"
```

## Writing Style

Write in **English only**.

Style guidelines — write like a human teammate, not a bot:

- Use plain paragraphs. Avoid headings (`##`), horizontal rules (`---`), and excessive bullet lists.
- Keep it conversational and direct. Say what matters, skip the filler.
- Do not use phrases like "Great point!" or "Thanks for raising this!" unless you genuinely mean it and have nothing else to add.
- Be honest. If you disagree or see an issue, say so clearly but respectfully.
- Short is fine. A two-sentence comment is better than a five-paragraph essay with no substance.

## Step 4: Report

Output the issue number and a brief summary of the comment that was posted.

© dyoshikawa · MIT · dyoshikawa/rulesync

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set21

release-dry-run This skill reviews changes since the latest release tag and recommends a MAJOR, MINOR, or PATCH bump. Use it to assess a release before changing the version. CX Codex +1 ★ 1,557repo stars rebase-latest-main A skill that walks the agent through fetching origin/main, rebasing the current branch and resolving conflicts. Handy when your branch has drifted behind main. CX Codex +1 ★ 1,557repo stars prs-awaiting-maintainer Finds open pull requests with passing checks that are waiting on a maintainer. Use it to list PRs ready for review, another review, or a merge decision. CX Codex +1 ★ 1,557repo stars prs-awaiting-author Lists open pull requests where the next move belongs to the author: failing CI, unaddressed review comments, or a maintainer question waiting on a reply. CX Codex +1 ★ 1,557repo stars porting-another-repository Reads a feature in your current repo and the target repo's conventions, then writes a porting plan into tmp/ as files you apply yourself. CX Codex +1 ★ 1,557repo stars goal-release Drives a release end to end: opens the PR, waits for green CI, merges it and updates the Homebrew formula. Handy when a version has to ship in one go. CX Codex +1 ★ 1,557repo stars goal-issues-and-release This skill processes open issues, then starts the release workflow. It makes routine choices on its own while keeping the stated safety checks in place. CX Codex +1 ★ 1,557repo stars git-worktree-runner A skill that teaches the agent to drive git worktrees through the gtr CLI: create, open in an editor, run commands, remove. CX Codex +1 ★ 1,557repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor