Run any Skill in Manus with one click

post-issue-comment

Stars1

Forks0

UpdatedJuly 22, 2026 at 05:29

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

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

dyoshikawa

dyoshikawa/webseek

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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 = $ARGUMENTS

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:

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.

More from this repository

same repository

approve

dyoshikawa/webseek

Approve a pull request using gh pr review --approve

2026-07-221

batch-review-prs-awaiting-maintainer

dyoshikawa/webseek

Batch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.

2026-07-221

clean-branches

dyoshikawa/webseek

Clean up unnecessary local branches and prune stale remote-tracking branches

2026-07-221

clean-worktrees

dyoshikawa/webseek

Clean git worktrees created by git-worktree-runner

2026-07-221

commit-push-pr

dyoshikawa/webseek

Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.

2026-07-221

diff-analyze

dyoshikawa/webseek

Analyze the differences between the current branch and origin/main, and summarize the current work progress

2026-07-221

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 = $ARGUMENTS

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:

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.