Add GitHub Comment
martin-ueding/geo-activity-playground
Style rules for commenting on GitHub Issues. An agent skill from martin-ueding/geo-activity-playground.
Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments
Install Post Issue Comment
$ npx skills add dyoshikawa/rulesync --skill post-issue-comment -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dyoshikawa/rulesync post-issue-comment --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.rulesync/skills/post-issue-comment .claude/skills/post-issue-comment && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "post-issue-comment" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-issue-comment into .claude/skills/post-issue-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-issue-comment", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-issue-commentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dyoshikawa/rulesync --skill post-issue-comment -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dyoshikawa/rulesync post-issue-comment --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.rulesync/skills/post-issue-comment .agents/skills/post-issue-comment && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "post-issue-comment" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-issue-comment into .agents/skills/post-issue-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-issue-comment", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dyoshikawa/rulesync --skill post-issue-comment -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dyoshikawa/rulesync post-issue-comment --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.rulesync/skills/post-issue-comment .cursor/skills/post-issue-comment && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "post-issue-comment" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-issue-comment into .cursor/skills/post-issue-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-issue-comment", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dyoshikawa/rulesync.git --path .rulesync/skills/post-issue-comment--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dyoshikawa/rulesync --skill post-issue-comment -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dyoshikawa/rulesync post-issue-comment --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.rulesync/skills/post-issue-comment .gemini/skills/post-issue-comment && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "post-issue-comment" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-issue-comment into .gemini/skills/post-issue-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-issue-comment", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dyoshikawa/rulesync post-issue-commentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dyoshikawa/rulesync --skill post-issue-comment -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .github/skills && cp -r skills-src/.rulesync/skills/post-issue-comment .github/skills/post-issue-comment && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "post-issue-comment" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-issue-comment into .github/skills/post-issue-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-issue-comment", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dyoshikawa/rulesync --skill post-issue-comment -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dyoshikawa/rulesync post-issue-comment --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.rulesync/skills/post-issue-comment .opencode/skills/post-issue-comment && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "post-issue-comment" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-issue-comment into .opencode/skills/post-issue-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-issue-comment", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
post-issue-comment- GitHub stars
- 1.5k
- Token cost
- ~541 tokens
- SKILL.md length
- 305 words
- Files
- 1
- Skills in repo
- 40
- Repo updated
- First seen
- Licence
- MIT
At a glance
Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments
- Works in 4 steps: Gather Issue Context → Draft the Reply → Post the Comment → …
- Tasks that involve Plain language and style rules
- SKILL.md covers Step 1: Gather Issue Context, Step 2: Draft the Reply, Step 3: Post the Comment and Writing Style, plus 1 more section
- Calls gh
What it does
Post Issue Comment is an agent skill from dyoshikawa/rulesync. Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments
Its SKILL.md is about 540 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Plain language and style rules. It works with GitHub. The repository describes itself as: A Utility CLI for AI Coding Agents. The licence is MIT.
When your agent uses it
- Tasks that involve Plain language and style rules
Example prompts
- “/post-issue-comment”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 85bcaf6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Post Issue Comment loads about 541 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 305 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dyoshikawa/rulesync at commit 85bcaf6, republished under its MIT licence (© dyoshikawa). 305 words, ~541 tokens.
Download SKILL.mdSave it as
.claude/skills/post-issue-comment/SKILL.md (or your agent's skills folder).- 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 tointent: 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
intentfaithfully; 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.
© dyoshikawa, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .rulesync/skills/post-issue-comment of dyoshikawa/rulesync.
Open the folder on GitHubat commit 85bcaf6
Compare with similar skills
Post Issue Comment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Post Issue Comment this skilldyoshikawa/rulesync | 1.5k | — | ~541 | Automated safety check: Pass | MIT | |
| Add GitHub Commentmartin-ueding/geo-activity-playground | 100 | — | ~225 | Automated safety check: Pass | Custom licence | |
| Routine From Chatrome-os/rome | 725 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Readability Checkjdevalk/skills | 104 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Repo System Maptamdogood/builder-essential-skills | 219 | — | ~3k | Automated safety check: Notes | MIT | |
| Git Teacher Statusfivetaku/gptaku-plugins-codex | 128 | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Routine From Chat
rome-os/rome
Turn a plain-language "do this automatically" request into a routine — either event-triggered ("text me when I get an email from my landlord") or scheduled ("remind me every Friday at 9am").
Readability Check
jdevalk/skills
Runs a readability audit on a blog post draft or other multi-paragraph prose, calibrated for readers who read English as a second language.
Repo System Map
tamdogood/builder-essential-skills
Analyze a software repository at the latest remote main commit and turn its implemented architecture into a citation-backed interactive isometric system map with a legend, selectable infrastructure…
Git Teacher Status
fivetaku/gptaku-plugins-codex
Translates current Git status into plain-language explanations for non-developers.
Issue Brief
VasiHemanth/tokentelemetry
Explain a GitHub issue, discussion, or feature request in plain language before deciding whether to build it.
More from dyoshikawa/rulesync
All 40 skills in this repoRulesync Feature Research
dyoshikawa/rulesync
Maps rulesync feature implementations to upstream coding-agent documentation.
Babysit Dependabot PR
dyoshikawa/rulesync
Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed)…
Commit Push PR
dyoshikawa/rulesync
Commit current changes, push to remote, and create or update a pull request.
Git Worktree Runner
dyoshikawa/rulesync
Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.
Goal PR
dyoshikawa/rulesync
Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge.
Goal Release
dyoshikawa/rulesync
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the…
Related
Works with
Categories
Questions about Post Issue Comment
What does Post Issue Comment do?
Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments. Post Issue Comment is an agent skill from dyoshikawa/rulesync.
When should I use Post Issue Comment?
Post Issue Comment fits situations like: tasks that involve Plain language and style rules.
How do I install Post Issue Comment in Claude Code?
Run `npx skills add dyoshikawa/rulesync --skill post-issue-comment -a claude-code`. Or copy the skill folder (.rulesync/skills/post-issue-comment in dyoshikawa/rulesync) into .claude/skills/post-issue-comment in your project. Claude Code loads it when a task matches its description.
How do I install Post Issue Comment in Codex?
Run `npx skills add dyoshikawa/rulesync --skill post-issue-comment -a codex`. Or copy the skill folder (.rulesync/skills/post-issue-comment in dyoshikawa/rulesync) into .agents/skills/post-issue-comment in your project. Codex loads it when a task matches its description.
Can I use Post Issue Comment in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dyoshikawa/rulesync --skill post-issue-comment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/post-issue-comment, .gemini/skills/post-issue-comment, .github/skills/post-issue-comment and .opencode/skills/post-issue-comment in your project.
What does Post Issue Comment need to run?
Going by SKILL.md and its folder, Post Issue Comment needs the command-line tools its instructions call (gh).
Does Post Issue Comment access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Post Issue Comment safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Post Issue Comment use?
Post Issue Comment is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Post Issue Comment use?
About 541 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Post Issue Comment?
Skills that share tags, products or a category with Post Issue Comment: Add GitHub Comment (martin-ueding/geo-activity-playground, 100 stars), Routine From Chat (rome-os/rome, 725 stars), Readability Check (jdevalk/skills, 104 stars) and Repo System Map (tamdogood/builder-essential-skills, 219 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Post Issue Comment?
dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,507 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 8, 2026.
Source: dyoshikawa/rulesync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.