Asd Ste100
danyuchn/asd-ste100-skill
A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…
Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style
Install Post Review Comments
$ npx skills add dyoshikawa/rulesync --skill post-review-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dyoshikawa/rulesync post-review-comments --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-review-comments .claude/skills/post-review-comments && 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-review-comments" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-review-comments into .claude/skills/post-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-review-comments", 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-review-commentsType 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-review-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dyoshikawa/rulesync post-review-comments --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-review-comments .agents/skills/post-review-comments && 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-review-comments" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-review-comments into .agents/skills/post-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-review-comments", 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-review-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dyoshikawa/rulesync post-review-comments --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-review-comments .cursor/skills/post-review-comments && 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-review-comments" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-review-comments into .cursor/skills/post-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-review-comments", 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-review-comments--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-review-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dyoshikawa/rulesync post-review-comments --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-review-comments .gemini/skills/post-review-comments && 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-review-comments" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-review-comments into .gemini/skills/post-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-review-comments", 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-review-commentsInstalls 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-review-comments -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-review-comments .github/skills/post-review-comments && 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-review-comments" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-review-comments into .github/skills/post-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-review-comments", 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-review-comments -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-review-comments --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-review-comments .opencode/skills/post-review-comments && 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-review-comments" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/post-review-comments into .opencode/skills/post-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-review-comments", 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-review-comments- GitHub stars
- 1.5k
- Token cost
- ~528 tokens
- SKILL.md length
- 265 words
- Files
- 1
- Skills in repo
- 40
- Repo updated
- First seen
- Licence
- MIT
At a glance
Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style
- Works in 5 steps: Understand the PR → Prepare Line-Level Comments → Prepare an Overall Review Comment → …
- Tasks that involve Plain language and style rules
- SKILL.md covers Step 1: Understand the PR, Step 2: Prepare Line-Level…, Step 3: Prepare an Overall… and Step 4: Post the Review, plus 2 more sections
- Calls gh
What it does
Post Review Comments is an agent skill from dyoshikawa/rulesync. Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style
Its SKILL.md is about 530 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. 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-review-comments”
Workflow steps
5 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 2c577d0. 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 Review Comments loads about 528 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 265 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 2c577d0, republished under its MIT licence (© dyoshikawa). 265 words, ~528 tokens.
Download SKILL.mdSave it as
.claude/skills/post-review-comments/SKILL.md (or your agent's skills folder).- name
- post-review-comments
- description
- Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style
- targets
- *
target_pr = the user's request
If target_pr is not provided, use the PR of the current branch.
Step 1: Understand the PR
Read the PR diff and description to understand:
- What changed and why
- The scope and impact of the changes
Step 2: Prepare Line-Level Comments
Identify specific lines in the diff that deserve feedback — bugs, potential issues, style concerns, suggestions for improvement, or questions about intent.
For each comment, note:
- The file path
- The line number (in the new version of the file)
- Your comment text
Step 3: Prepare an Overall Review Comment
Write a brief overall assessment of the PR. This is a summary-level comment, not a repeat of line-level feedback.
Step 4: Post the Review
Use a single gh api call to submit both line-level comments and the overall comment together as one review:
gh api repos/{owner}/{repo}/pulls/{pr_number}/reviews \
--method POST \
-f event="COMMENT" \
-f body="<overall comment>" \
-f 'comments[]={...}' ...Each line comment requires: path, line (line number in the diff's new file), and body.
If you have no line-level comments, fall back to:
gh pr review <pr_number> --comment --body "<overall comment>"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 work!" or "LGTM!" unless you genuinely mean it and have nothing else to add.
- Be honest. If something looks off, say so clearly but respectfully.
- Short is fine. A two-sentence comment is better than a five-paragraph essay with no substance.
Step 5: Report
Output the PR number, a count of line-level comments posted, and a brief summary of the overall comment.
© 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-review-comments of dyoshikawa/rulesync.
Open the folder on GitHubat commit 2c577d0
Compare with similar skills
Post Review Comments 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 Review Comments this skilldyoshikawa/rulesync | 1.5k | — | ~528 | Automated safety check: Pass | MIT | |
| Asd Ste100danyuchn/asd-ste100-skill | 4.2k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Simple Issue Descriptionevery-app/open-seo | 23k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Ponytail AuditDietrichGebert/ponytail | 159k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 10k | 10 repos | ~2.4k | Automated safety check: Pass | None | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Simple Issue Description
every-app/open-seo
Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior.
Ponytail Audit
DietrichGebert/ponytail
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
Pgjev
realZachi/pg-jev
Install, configure, query and explain pgjev (the jev PostgreSQL extension that filters, ranks and classifies rows with plain-language conditions via TypeSafe's Jev model).
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
Categories
Questions about Post Review Comments
What does Post Review Comments do?
Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style. Post Review Comments is an agent skill from dyoshikawa/rulesync.
When should I use Post Review Comments?
Post Review Comments fits situations like: tasks that involve Plain language and style rules.
How do I install Post Review Comments in Claude Code?
Run `npx skills add dyoshikawa/rulesync --skill post-review-comments -a claude-code`. Or copy the skill folder (.rulesync/skills/post-review-comments in dyoshikawa/rulesync) into .claude/skills/post-review-comments in your project. Claude Code loads it when a task matches its description.
How do I install Post Review Comments in Codex?
Run `npx skills add dyoshikawa/rulesync --skill post-review-comments -a codex`. Or copy the skill folder (.rulesync/skills/post-review-comments in dyoshikawa/rulesync) into .agents/skills/post-review-comments in your project. Codex loads it when a task matches its description.
Can I use Post Review Comments 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-review-comments -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-review-comments, .gemini/skills/post-review-comments, .github/skills/post-review-comments and .opencode/skills/post-review-comments in your project.
What does Post Review Comments need to run?
Going by SKILL.md and its folder, Post Review Comments needs the command-line tools its instructions call (gh).
Does Post Review Comments 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 Review Comments 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 Review Comments use?
Post Review Comments 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 Review Comments use?
About 528 tokens (SKILL.md is roughly 2.1k 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 Review Comments?
Skills that share tags, products or a category with Post Review Comments: Asd Ste100 (danyuchn/asd-ste100-skill, 4.2k stars), Simple Issue Description (every-app/open-seo, 23k stars), Ponytail Audit (DietrichGebert/ponytail, 159k stars) and Technical Writing Standard (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Post Review Comments?
dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,508 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 9, 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.