Repomix Browser Extension Developer
yamadashy/repomix
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content…
Investigate or fix a referenced Voyager GitHub issue, within the requested delivery scope.
GPL-3.0Auto-check passed
Install Issue Review
$ npx skills add voyager-crew/voyager --skill issue-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install voyager-crew/voyager issue-review --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/voyager-crew/voyager.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/issue-review .claude/skills/issue-review && 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 "issue-review" agent skill from https://github.com/voyager-crew/voyager/tree/main/.agents/skills/issue-review into .claude/skills/issue-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-review", 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/voyager-crew/voyager/tree/main/.agents/skills/issue-reviewType 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 voyager-crew/voyager --skill issue-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install voyager-crew/voyager issue-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/voyager-crew/voyager.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/issue-review .agents/skills/issue-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-review" agent skill from https://github.com/voyager-crew/voyager/tree/main/.agents/skills/issue-review into .agents/skills/issue-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-review", 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 voyager-crew/voyager --skill issue-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install voyager-crew/voyager issue-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/voyager-crew/voyager.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/issue-review .cursor/skills/issue-review && 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 "issue-review" agent skill from https://github.com/voyager-crew/voyager/tree/main/.agents/skills/issue-review into .cursor/skills/issue-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-review", 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/voyager-crew/voyager.git --path .agents/skills/issue-review--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 voyager-crew/voyager --skill issue-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install voyager-crew/voyager issue-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/voyager-crew/voyager.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/issue-review .gemini/skills/issue-review && 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 "issue-review" agent skill from https://github.com/voyager-crew/voyager/tree/main/.agents/skills/issue-review into .gemini/skills/issue-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-review", 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 voyager-crew/voyager issue-reviewInstalls 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 voyager-crew/voyager --skill issue-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/voyager-crew/voyager.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/issue-review .github/skills/issue-review && 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 "issue-review" agent skill from https://github.com/voyager-crew/voyager/tree/main/.agents/skills/issue-review into .github/skills/issue-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-review", 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 voyager-crew/voyager --skill issue-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install voyager-crew/voyager issue-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/voyager-crew/voyager.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/issue-review .opencode/skills/issue-review && 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 "issue-review" agent skill from https://github.com/voyager-crew/voyager/tree/main/.agents/skills/issue-review into .opencode/skills/issue-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-review", 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
issue-review- GitHub stars
- 20k
- Token cost
- ~289 tokens
- SKILL.md length
- 157 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Investigate or fix a referenced Voyager GitHub issue, within the requested delivery scope.
- Works in 4 steps: Begin with gh issue view --comments (add… → Match completion to the request:… → When the request includes committing or… → …
- Calls gh and git
What it does
Issue Review is an agent skill from voyager-crew/voyager. Investigate or fix a referenced Voyager GitHub issue, within the requested delivery scope.
Its SKILL.md is about 290 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It works with GitHub and Chrome Extensions. The repository describes itself as: Enhancement suite for Gemini, AI Studio, Claude, ChatGPT & DeepSeek — plus a prompt manager for any website, DeepSeek Harness included. / 面向 Gemini、AI Studio、Claude、ChatGPT 与… The licence is GPL-3.0.
Example prompts
- “/issue-review”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Begin with gh issue view --comments (add --repo owner/repo when needed). Read the actual issue before locating the cause in the repository.
- Match completion to the request: investigation delivers evidence, root cause or remaining uncertainty, and a recommended fix…
- When the request includes committing or publishing, use voyager-contribute. A fix commit or PR includes Closes # or Fixes #; verify any…
- When authorized to post, report the actual status in the reporter's language. Say the fix has landed and is coming in the next version…
What it can do on your machine
Read from SKILL.md and the folder at commit e854e34. 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:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, 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
Issue Review loads about 289 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 157 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 voyager-crew/voyager at commit e854e34, republished under its GPL-3.0 licence (© voyager-crew). 157 words, ~289 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- issue-review
- description
- Investigate or fix a referenced Voyager GitHub issue, within the requested delivery scope.
Issue Review
- Begin with
gh issue view <number-or-url> --comments(add--repo owner/repowhen needed). Read the actual issue before locating the cause in the repository. - Match completion to the request: investigation delivers evidence, root cause or remaining uncertainty, and a recommended fix; implementation delivers the scoped change and applicable verification from
AGENTS.md. - When the request includes committing or publishing, use
voyager-contribute. A fix commit or PR includesCloses #<number>orFixes #<number>; verify any created commit withgit show --stat --format=fuller HEAD. An investigation or uncommitted fix needs no commit inspection. - When authorized to post, report the actual status in the reporter's language. Say the fix has landed and is coming in the next version only after it has landed. Close the issue only when the fix has landed or another agreed resolution is satisfied and closing is authorized; a local fix or an open PR alone is not completion of the issue.
© voyager-crew, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/issue-review of voyager-crew/voyager.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit e854e34
Compare with similar skills
Issue Review 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 |
|---|---|---|---|---|---|---|
| Issue Review this skillvoyager-crew/voyager | 20k | — | ~289 | Automated safety check: Pass | GPL-3.0 | |
| Repomix Browser Extension Developeryamadashy/repomix | 29k | 1 repos | ~288 | Automated safety check: Pass | MIT | |
| Deepseek Automationzhu1090093659/deepseek-pp | 1.9k | — | ~2.1k | Automated safety check: Notes | Apache-2.0 | |
| Spec Driven Developzhu1090093659/deepseek-pp | 1.9k | — | ~6.9k | Automated safety check: Pass | Apache-2.0 | |
| Chrome Relayaindeev/agent-chrome-relay | 249 | — | ~669 | Automated safety check: Pass | MIT | |
| Release ExtensionYorick-Ryu/deep-share | 144 | — | ~1.3k | Automated safety check: Pass | Custom licence |
Similar skills
Deepseek Automation
zhu1090093659/deepseek-pp
A skill your agent uses when implementing, resuming, reviewing, or verifying the DeepSeek++ Codex-style automation feature in this repository.
Spec Driven Develop
zhu1090093659/deepseek-pp
Automates pre-development workflow for large-scale complex tasks.
Chrome Relay
aindeev/agent-chrome-relay
Use the person's own signed-in Chrome from the command line, in background tabs, through Chrome Relay.
Release Extension
Yorick-Ryu/deep-share
Release browser extensions or similar small packaged apps by upgrading a semantic version, packaging build artifacts, creating a git commit and tag, pushing to the remote, and publishing a GitHub…
Land PR
ZenUml/web-sequence
Merge a green ZenUML web-sequence PR into master and verify staging CI after merge.
More from voyager-crew/voyager
Create Voyager Plugin
voyager-crew/voyager
Create or change a Voyager declarative plugin, site adapter, or native primitive.
Release
voyager-crew/voyager
Prepare, publish, or recover a Voyager release. An agent skill from voyager-crew/voyager.
Voyager Contribute
voyager-crew/voyager
Prepare Voyager commits, pull requests, and contribution evidence, or claim an issue and check review readiness.
Update Safari Extension
voyager-crew/voyager
Build, reload, and verify Voyager in Safari for web-extension changes, native integration, or signed-app testing while preserving installed apps and extension data.
Verify In Browser
voyager-crew/voyager
Verify Voyager content-script or injected-CSS behavior in a live browser, including stale-build diagnosis.
PR Description
voyager-crew/voyager
Write or rewrite a Voyager pull request description. An agent skill from voyager-crew/voyager.
Related
Works with
Questions about Issue Review
What does Issue Review do?
Investigate or fix a referenced Voyager GitHub issue, within the requested delivery scope. Issue Review is an agent skill from voyager-crew/voyager. Investigate or fix a referenced Voyager GitHub issue, within the requested delivery scope.
How do I install Issue Review in Claude Code?
Run `npx skills add voyager-crew/voyager --skill issue-review -a claude-code`. Or copy the skill folder (.agents/skills/issue-review in voyager-crew/voyager) into .claude/skills/issue-review in your project. Claude Code loads it when a task matches its description.
How do I install Issue Review in Codex?
Run `npx skills add voyager-crew/voyager --skill issue-review -a codex`. Or copy the skill folder (.agents/skills/issue-review in voyager-crew/voyager) into .agents/skills/issue-review in your project. Codex loads it when a task matches its description.
Can I use Issue Review 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 voyager-crew/voyager --skill issue-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-review, .gemini/skills/issue-review, .github/skills/issue-review and .opencode/skills/issue-review in your project.
What does Issue Review need to run?
Going by SKILL.md and its folder, Issue Review needs the command-line tools its instructions call (gh and git).
Does Issue Review access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Issue Review 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 Issue Review use?
Issue Review is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Issue Review use?
About 289 tokens (SKILL.md is roughly 1.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 Issue Review?
Skills that share tags, products or a category with Issue Review: Repomix Browser Extension Developer (yamadashy/repomix, 29k stars), Deepseek Automation (zhu1090093659/deepseek-pp, 1.9k stars), Spec Driven Develop (zhu1090093659/deepseek-pp, 1.9k stars) and Chrome Relay (aindeev/agent-chrome-relay, 249 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue Review?
voyager-crew (a GitHub organization) maintains it in voyager-crew/voyager, which has 20,349 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 10, 2026.
Source: voyager-crew/voyager on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.