GitHub Commenting
juspay/neurolink
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules.
Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.
Install Project Pull Request
$ npx skills add swimmwatch/cloakbrowser-mcp --skill project-pull-request -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install swimmwatch/cloakbrowser-mcp project-pull-request --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/swimmwatch/cloakbrowser-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/project-pull-request .claude/skills/project-pull-request && 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 "project-pull-request" agent skill from https://github.com/swimmwatch/cloakbrowser-mcp/tree/main/.agents/skills/project-pull-request into .claude/skills/project-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-pull-request", 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/swimmwatch/cloakbrowser-mcp/tree/main/.agents/skills/project-pull-requestType 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 swimmwatch/cloakbrowser-mcp --skill project-pull-request -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install swimmwatch/cloakbrowser-mcp project-pull-request --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swimmwatch/cloakbrowser-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/project-pull-request .agents/skills/project-pull-request && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "project-pull-request" agent skill from https://github.com/swimmwatch/cloakbrowser-mcp/tree/main/.agents/skills/project-pull-request into .agents/skills/project-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-pull-request", 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 swimmwatch/cloakbrowser-mcp --skill project-pull-request -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install swimmwatch/cloakbrowser-mcp project-pull-request --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swimmwatch/cloakbrowser-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/project-pull-request .cursor/skills/project-pull-request && 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 "project-pull-request" agent skill from https://github.com/swimmwatch/cloakbrowser-mcp/tree/main/.agents/skills/project-pull-request into .cursor/skills/project-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-pull-request", 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/swimmwatch/cloakbrowser-mcp.git --path .agents/skills/project-pull-request--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 swimmwatch/cloakbrowser-mcp --skill project-pull-request -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install swimmwatch/cloakbrowser-mcp project-pull-request --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swimmwatch/cloakbrowser-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/project-pull-request .gemini/skills/project-pull-request && 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 "project-pull-request" agent skill from https://github.com/swimmwatch/cloakbrowser-mcp/tree/main/.agents/skills/project-pull-request into .gemini/skills/project-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-pull-request", 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 swimmwatch/cloakbrowser-mcp project-pull-requestInstalls 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 swimmwatch/cloakbrowser-mcp --skill project-pull-request -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/swimmwatch/cloakbrowser-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/project-pull-request .github/skills/project-pull-request && 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 "project-pull-request" agent skill from https://github.com/swimmwatch/cloakbrowser-mcp/tree/main/.agents/skills/project-pull-request into .github/skills/project-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-pull-request", 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 swimmwatch/cloakbrowser-mcp --skill project-pull-request -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install swimmwatch/cloakbrowser-mcp project-pull-request --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swimmwatch/cloakbrowser-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/project-pull-request .opencode/skills/project-pull-request && 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 "project-pull-request" agent skill from https://github.com/swimmwatch/cloakbrowser-mcp/tree/main/.agents/skills/project-pull-request into .opencode/skills/project-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-pull-request", 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
project-pull-request- GitHub stars
- 161
- Token cost
- ~1k tokens
- SKILL.md length
- 548 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.
- Explicitly requests PR work
- SKILL.md covers Authorization, Preconditions, Assignee and Title, plus 2 more sections
- Calls npm, git and gh; reaches conventionalcommits.org
- Tasks that involve Pull requests
What it does
Project Pull Request is an agent skill from swimmwatch/cloakbrowser-mcp. Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work. Follow the repository's branch, base/head, assignee, title, template, check, security, and reporting rules; review remains read-only, and commit, push, PR creation/update, readiness changes, merge, and other external mutations each require explicit authorization.
Its SKILL.md is about 1k 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 Browser automation. It works with Model Context Protocol, GitHub, Playwright and Docker. The repository describes itself as: ⚡ CloakBrowser MCP server for AI agents: Playwright-powered browsing, clean tool forwarding, Docker support, and multi-session HTTP transport. The licence is MIT.
When your agent uses it
- Explicitly requests PR work
- Tasks that involve Pull requests
- Tasks that involve MCP servers
Example prompts
- “/project-pull-request”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit 7e5ddd0. 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:
npmgitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
conventionalcommits.org
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
Project Pull Request loads about 1k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 548 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 swimmwatch/cloakbrowser-mcp at commit 7e5ddd0, republished under its MIT licence (© swimmwatch). 548 words, ~1,039 tokens.
Download SKILL.mdSave it as
.claude/skills/project-pull-request/SKILL.md (or your agent's skills folder).- name
- project-pull-request
- description
- Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work. Follow the repository's branch, base/head, assignee, title, template, check, security, and reporting rules; review remains read-only, and commit, push, PR creation/update, readiness changes, merge, and other external mutations each require explicit authorization.
Project Pull Request
Use this skill for cloakbrowser-mcp Pull Request work. The repository's
.github/PULL_REQUEST_TEMPLATE.md is the required PR body format; do not
replace it with a second template.
Authorization
- A request to review or prepare a PR does not authorize edits, commits, pushes, PR creation/update, readiness changes, merge, or branch deletion.
- Before each external mutation, confirm that the user explicitly authorized that action. Use the global Prompt MCP for any unresolved material base, head, assignee, readiness, scope, or execution choice.
- Never infer push or PR authorization from approval of code, a specification, a plan, local checks, or a commit.
- Preserve unrelated worktree changes and stage only the intended PR scope.
Preconditions
- Inspect
git status, current branch, upstream tracking, and diff before creating or updating a PR. - Do not open a PR from
main. - Use
mainas the base branch unless the user explicitly gives another base. - Before creating a commit for the PR, open and scan
https://www.conventionalcommits.org/en/v1.0.0/. - Obtain explicit commit authorization before creating the commit.
- Run
npm run checklocally after the final edits and before creating a commit. If it fails, fix the failure or report the blocker; do not commit. - If any file changes after
npm run check, rerunnpm run checkbefore committing. - After explicit push authorization, push the current feature branch to
originbefore creating the PR. - Run
npm run checkagain on the committed branch before pushing. If it fails, fix the failure or report the blocker; do not push or create/update the PR. - Create PRs ready for review by default. Use draft only when the user explicitly asks for a draft PR.
Assignee
- Assign the PR to the authenticated GitHub user by default. Resolve the login
with
gh api user --jq .loginor the equivalent GitHub connector identity. - For this repository, the expected default assignee is
swimmwatchunless the user explicitly requests another assignee. - If the assignee cannot be resolved or GitHub rejects it, report the blocker and leave the PR otherwise complete.
Show full SKILL.md (219 more words)Show less
Title
- Use a concise Conventional-style title, such as
build(deps): bump cloakbrowser to 0.3.31. - Use imperative or present-tense wording after the conventional prefix.
- Make the title describe the main branch change, not a test result or implementation detail.
Body
Fill every section from .github/PULL_REQUEST_TEMPLATE.md:
Summary: include 2-4 bullets explaining what changed and why.Checklist: keep every template item. Mark[x]only when completed. If an item is not applicable, keep it visible and add a short reason.Security review: write explicit notes even when there is no new risk. Mention bridge, child-process, filesystem, Docker, logging, secrets/tokens, OIDC, and registry publishing when relevant.Test evidence: list exact commands and outcomes. If a relevant check was skipped, state why.- Do not mark
npm run checkcomplete unless it passed locally on the branch being pushed.
Do not leave HTML comments or placeholder text in the submitted PR body.
Create Or Update
- Obtain explicit authorization for the exact PR creation or update before mutating GitHub.
- Prefer the available GitHub app or connector. Use
ghwhen connector support is unavailable or insufficient. - If a PR already exists for the branch, update its title/body instead of creating a duplicate.
- After creating or updating the PR, report the PR URL, base/head branches, title, assignee, whether it is draft or ready for review, and any skipped checks.
© swimmwatch, 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 .agents/skills/project-pull-request of swimmwatch/cloakbrowser-mcp.
Open the folder on GitHubat commit 7e5ddd0
Compare with similar skills
Project Pull Request 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 |
|---|---|---|---|---|---|---|
| Project Pull Request this skillswimmwatch/cloakbrowser-mcp | 161 | — | ~1k | Automated safety check: Pass | MIT | |
| GitHub Commentingjuspay/neurolink | 143 | — | ~698 | Automated safety check: Pass | MIT | |
| Code Reviewnteract/semiotic | 2.7k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Devcontainer Devstacklok/toolhive-studio | 170 | — | ~3.8k | Automated safety check: Notes | Apache-2.0 | |
| Skillredf0x1/camofox-mcp | 117 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Open Supermarketsabracadabra50/open-supermarkets | 117 | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Code Review
nteract/semiotic
Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence.
Devcontainer Dev
stacklok/toolhive-studio
Spin up and interact with ToolHive Studio's containerized dev environment (Xvfb + noVNC + DinD).
Skill
redf0x1/camofox-mcp
Anti-detection browser automation MCP skill for OpenClaw agents with 47 tools for navigation, interaction, observation, extraction, downloads, profiles, sessions, and stealth web search.
Open Supermarkets
abracadabra50/open-supermarkets
Searches, compares and fills baskets across supermarkets in several countries, with delivery slots, checkout and nutrition data, as a CLI, MCP server or skill.
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.
More from swimmwatch/cloakbrowser-mcp
Project Release
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
Project Docs Maintainer
swimmwatch/cloakbrowser-mcp
Maintain, organize, consolidate, or audit the cloakbrowser-mcp documentation set only when the user explicitly requests project documentation maintenance or an authorized public change requires it.
Related
Questions about Project Pull Request
What does Project Pull Request do?
Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work. Project Pull Request is an agent skill from swimmwatch/cloakbrowser-mcp. Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.
When should I use Project Pull Request?
Project Pull Request fits situations like: explicitly requests PR work; tasks that involve Pull requests; tasks that involve MCP servers.
How do I install Project Pull Request in Claude Code?
Run `npx skills add swimmwatch/cloakbrowser-mcp --skill project-pull-request -a claude-code`. Or copy the skill folder (.agents/skills/project-pull-request in swimmwatch/cloakbrowser-mcp) into .claude/skills/project-pull-request in your project. Claude Code loads it when a task matches its description.
How do I install Project Pull Request in Codex?
Run `npx skills add swimmwatch/cloakbrowser-mcp --skill project-pull-request -a codex`. Or copy the skill folder (.agents/skills/project-pull-request in swimmwatch/cloakbrowser-mcp) into .agents/skills/project-pull-request in your project. Codex loads it when a task matches its description.
Can I use Project Pull Request 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 swimmwatch/cloakbrowser-mcp --skill project-pull-request -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-pull-request, .gemini/skills/project-pull-request, .github/skills/project-pull-request and .opencode/skills/project-pull-request in your project.
What does Project Pull Request need to run?
Going by SKILL.md and its folder, Project Pull Request needs the command-line tools its instructions call (npm, git and gh). Our summary lists: Docker.
Does Project Pull Request access the network?
SKILL.md names 1 domain. In commands or code: conventionalcommits.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Project Pull Request 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 Project Pull Request use?
Project Pull Request 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 Project Pull Request use?
About 1k tokens (SKILL.md is roughly 4.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 Project Pull Request?
Skills that share tags, products or a category with Project Pull Request: GitHub Commenting (juspay/neurolink, 143 stars), Code Review (nteract/semiotic, 2.7k stars), Devcontainer Dev (stacklok/toolhive-studio, 170 stars) and Skill (redf0x1/camofox-mcp, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Project Pull Request?
swimmwatch (a GitHub user) maintains it in swimmwatch/cloakbrowser-mcp, which has 161 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 1, 2026.
Source: swimmwatch/cloakbrowser-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.