Project Pull Request
swimmwatch/cloakbrowser-mcp
Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules.
Install GitHub Commenting
$ npx skills add juspay/neurolink --skill github-commenting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install juspay/neurolink github-commenting --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/juspay/neurolink.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.yama/skills/github-commenting .claude/skills/github-commenting && 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 "github-commenting" agent skill from https://github.com/juspay/neurolink/tree/release/.yama/skills/github-commenting into .claude/skills/github-commenting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-commenting", 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/juspay/neurolink/tree/release/.yama/skills/github-commentingType 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 juspay/neurolink --skill github-commenting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install juspay/neurolink github-commenting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/juspay/neurolink.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.yama/skills/github-commenting .agents/skills/github-commenting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-commenting" agent skill from https://github.com/juspay/neurolink/tree/release/.yama/skills/github-commenting into .agents/skills/github-commenting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-commenting", 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 juspay/neurolink --skill github-commenting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install juspay/neurolink github-commenting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/juspay/neurolink.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.yama/skills/github-commenting .cursor/skills/github-commenting && 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 "github-commenting" agent skill from https://github.com/juspay/neurolink/tree/release/.yama/skills/github-commenting into .cursor/skills/github-commenting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-commenting", 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/juspay/neurolink.git --path .yama/skills/github-commenting--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 juspay/neurolink --skill github-commenting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install juspay/neurolink github-commenting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/juspay/neurolink.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.yama/skills/github-commenting .gemini/skills/github-commenting && 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 "github-commenting" agent skill from https://github.com/juspay/neurolink/tree/release/.yama/skills/github-commenting into .gemini/skills/github-commenting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-commenting", 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 juspay/neurolink github-commentingInstalls 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 juspay/neurolink --skill github-commenting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/juspay/neurolink.git skills-src && mkdir -p .github/skills && cp -r skills-src/.yama/skills/github-commenting .github/skills/github-commenting && 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 "github-commenting" agent skill from https://github.com/juspay/neurolink/tree/release/.yama/skills/github-commenting into .github/skills/github-commenting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-commenting", 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 juspay/neurolink --skill github-commenting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install juspay/neurolink github-commenting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/juspay/neurolink.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.yama/skills/github-commenting .opencode/skills/github-commenting && 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 "github-commenting" agent skill from https://github.com/juspay/neurolink/tree/release/.yama/skills/github-commenting into .opencode/skills/github-commenting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-commenting", 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
github-commenting- GitHub stars
- 143
- Token cost
- ~698 tokens
- SKILL.md length
- 378 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules.
- Works in 2 steps: List the existing review comments AND… → Every comment you post starts with an…
- Tasks that involve Pull requests
- SKILL.md covers Before posting anything, Inline comments, Suggestion blocks — a fix the… and Formatting for humans, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
GitHub Commenting is an agent skill from juspay/neurolink. How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
Its SKILL.md is about 700 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 Development, covering Pull requests, MCP servers and Text to speech and voice. It works with GitHub, Model Context Protocol, OpenAI and Vercel AI SDK. The repository describes itself as: The pipe layer of an AI nervous system — one interface connecting provider neurons to your application, across three inference types: generate, stream, and a calibrated decide… The licence is MIT.
When your agent uses it
- Tasks that involve Pull requests
- Tasks that involve MCP servers
- Tasks that involve Text to speech and voice
Example prompts
- “/github-commenting”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- List the existing review comments AND issue comments on the pull request first.
- Every comment you post starts with an invisible marker line: <!-- yama: -->. If a marker for the same finding already exists, do NOT post…
What it can do on your machine
Read from SKILL.md and the folder at commit 171cc74. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
GitHub Commenting loads about 698 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 378 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 juspay/neurolink at commit 171cc74, republished under its MIT licence (© juspay). 378 words, ~698 tokens.
Download SKILL.mdSave it as
.claude/skills/github-commenting/SKILL.md (or your agent's skills folder).- name
- github-commenting
- description
- How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
Clean GitHub PR commenting
Before posting anything
- List the existing review comments AND issue comments on the pull request first.
- Every comment you post starts with an invisible marker line:
<!-- yama:<stable-finding-id> -->. If a marker for the same finding already exists, do NOT post it again — update that comment if it needs fixing, otherwise leave it alone.
Inline comments
- Anchor to the exact file and line in the DIFF. A line that is not part of the diff cannot hold a comment — anchor to the nearest changed line and say so.
- Multi-line ranges:
start_lineis the first line,lineis the last;side/start_sideareRIGHTfor added lines andLEFTfor deleted ones. - Tool shapes differ: some GitHub MCP servers post an inline comment in one call; the hosted server may require the pending-review lifecycle (create review → add comments → submit). If a pending review is opened it MUST be submitted — both or neither, never half.
Suggestion blocks — a fix the author applies in one click
Explain the issue in one or two sentences ABOVE the block, then:
```suggestion
the replacement for the entire anchored line range
```- The block's body replaces the WHOLE
start_line..linerange — include every line of the range, exactly indented. - If the replacement itself contains triple backticks (markdown files, code fences), use a four-backtick outer fence (
````suggestion) so GitHub does not close the block early. - Prefer a suggestion block whenever you propose a concrete code fix - it is the fix the author applies in one click, and an inline comment about a code change should normally carry one. Fall back to prose only when the right code is genuinely uncertain.
Show full SKILL.md (115 more words)Show less
Formatting for humans
- One finding per comment: severity (CRITICAL / MAJOR / MINOR), what breaks, why it matters here, and the fix.
- Cite rulebook ids where they apply.
- Evidence longer than ~10 lines goes in a collapsible section:
<details><summary>evidence</summary>…</details>. - Prefer short headers, tables and task lists over walls of prose. No emoji noise.
The one summary comment
Post exactly ONE summary comment (an issue comment on the PR), marker <!-- yama:summary -->:
- verdict at the top (APPROVE or NEEDS_WORK), one sentence of rationale,
- a short table of findings — severity,
file:line, one-line description, - what was checked and found clean, so silence is distinguishable from absence.
If a comment with that marker already exists, UPDATE it — never add a second summary.
© juspay, 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 .yama/skills/github-commenting of juspay/neurolink.
Open the folder on GitHubat commit 171cc74
Compare with similar skills
GitHub Commenting 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 |
|---|---|---|---|---|---|---|
| GitHub Commenting this skilljuspay/neurolink | 143 | — | ~698 | Automated safety check: Pass | MIT | |
| Project Pull Requestswimmwatch/cloakbrowser-mcp | 161 | — | ~1k | Automated safety check: Pass | MIT | |
| Chatgpt App Builderalpic-ai/skybridge | 2.1k | — | ~1k | Automated safety check: Pass | MIT | |
| Code Reviewnteract/semiotic | 2.7k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Open PRArcadeAI/arcade-mcp | 1k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Skybridgealpic-ai/skybridge | 2.1k | — | ~923 | Automated safety check: Pass | MIT |
Similar skills
Chatgpt App Builder
alpic-ai/skybridge
Guide developers through creating and updating ChatGPT plugins.
Code Review
nteract/semiotic
Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence.
Open PR
ArcadeAI/arcade-mcp
Prepare arcade-mcp changes for review by verifying intended behavior, filling the repository PR template, and creating or updating the PR.
Skybridge
alpic-ai/skybridge
Guide developers through creating and updating ChatGPT plugins and MCP Apps.
PR Review
confluentinc/mcp-confluent
Reviews pull requests for the Confluent MCP server. An agent skill from confluentinc/mcp-confluent.
More from juspay/neurolink
Neurolink Guide
juspay/neurolink
Guide for using the NeuroLink SDK and CLI. An agent skill from juspay/neurolink.
Repo Conventions
juspay/neurolink
NeuroLink's review standards — the critical rules to enforce, what NOT to comment on, the security bar, hot paths.
Related
Questions about GitHub Commenting
What does GitHub Commenting do?
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. GitHub Commenting is an agent skill from juspay/neurolink. How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules.
When should I use GitHub Commenting?
GitHub Commenting fits situations like: tasks that involve Pull requests; tasks that involve MCP servers; tasks that involve Text to speech and voice.
How do I install GitHub Commenting in Claude Code?
Run `npx skills add juspay/neurolink --skill github-commenting -a claude-code`. Or copy the skill folder (.yama/skills/github-commenting in juspay/neurolink) into .claude/skills/github-commenting in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Commenting in Codex?
Run `npx skills add juspay/neurolink --skill github-commenting -a codex`. Or copy the skill folder (.yama/skills/github-commenting in juspay/neurolink) into .agents/skills/github-commenting in your project. Codex loads it when a task matches its description.
Can I use GitHub Commenting 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 juspay/neurolink --skill github-commenting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-commenting, .gemini/skills/github-commenting, .github/skills/github-commenting and .opencode/skills/github-commenting in your project.
What does GitHub Commenting need to run?
SKILL.md names no scripts, command-line tools or credentials: GitHub Commenting is instructions for the agent only.
Does GitHub Commenting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is GitHub Commenting 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 GitHub Commenting use?
GitHub Commenting 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 GitHub Commenting use?
About 698 tokens (SKILL.md is roughly 2.8k 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 GitHub Commenting?
Skills that share tags, products or a category with GitHub Commenting: Project Pull Request (swimmwatch/cloakbrowser-mcp, 161 stars), Chatgpt App Builder (alpic-ai/skybridge, 2.1k stars), Code Review (nteract/semiotic, 2.7k stars) and Open PR (ArcadeAI/arcade-mcp, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub Commenting?
juspay (a GitHub organization) maintains it in juspay/neurolink, which has 143 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: juspay/neurolink on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.