Git Worktree Runner
dyoshikawa/rulesync
Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.
Push a Forge worktree branch, create a PR, and delegate review through the Forge Codex review adapter.
Install Work On Review
$ npx skills add RapierCraftStudios/ForgeDock --skill work-on-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on-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/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/work-on/review .claude/skills/work-on-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 "work-on-review" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/review into .claude/skills/work-on-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-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/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/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 RapierCraftStudios/ForgeDock --skill work-on-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/work-on/review .agents/skills/work-on-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 "work-on-review" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/review into .agents/skills/work-on-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-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 RapierCraftStudios/ForgeDock --skill work-on-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/work-on/review .cursor/skills/work-on-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 "work-on-review" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/review into .cursor/skills/work-on-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-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/RapierCraftStudios/ForgeDock.git --path .agents/skills/work-on/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 RapierCraftStudios/ForgeDock --skill work-on-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/work-on/review .gemini/skills/work-on-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 "work-on-review" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/review into .gemini/skills/work-on-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-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 RapierCraftStudios/ForgeDock work-on-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 RapierCraftStudios/ForgeDock --skill work-on-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/work-on/review .github/skills/work-on-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 "work-on-review" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/review into .github/skills/work-on-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-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 RapierCraftStudios/ForgeDock --skill work-on-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 RapierCraftStudios/ForgeDock work-on-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/work-on/review .opencode/skills/work-on-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 "work-on-review" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/review into .opencode/skills/work-on-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-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
work-on-review- GitHub stars
- 117
- Token cost
- ~436 tokens
- SKILL.md length
- 193 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Push a Forge worktree branch, create a PR, and delegate review through the Forge Codex review adapter.
- Tasks that involve Git worktrees
- SKILL.md covers Review Delegation Override, Review Focus for Forge PRs and Continuation Rule
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Work On Review is an agent skill from RapierCraftStudios/ForgeDock. Push a Forge worktree branch, create a PR, and delegate review through the Forge Codex review adapter.
Its SKILL.md is about 440 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 Git worktrees. It works with GitHub. The repository describes itself as: ForgeDock — autonomous AI dev pipeline for Claude Code. GitHub as agent memory: issue in, PR out. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve Git worktrees
Example prompts
- “/work-on-review”
What it can do on your machine
Read from SKILL.md and the folder at commit d89c6f2. 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.
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
Work On Review loads about 436 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 193 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 RapierCraftStudios/ForgeDock at commit d89c6f2, republished under its AGPL-3.0 licence (© RapierCraftStudios). 193 words, ~436 tokens.
Download SKILL.mdSave it as
.claude/skills/work-on-review/SKILL.md (or your agent's skills folder).- name
- work-on-review
- description
- Push a Forge worktree branch, create a PR, and delegate review through the Forge Codex review adapter.
Forge Repo Adapter: work-on/review
Use commands/work-on/review.md as the authoritative PR-creation workflow, with these Forge repo overrides:
- Default repo context is
RapierCraftStudios/forgedock. - After push/PR creation, route review to the repo-local Forge review adapter instead of assuming the project’s external review environment.
- Preserve
FORGE:REVIEW_STARTED,REVIEW_RESULT, merge verification, and issue-closing behavior from the shared workflow.
Review Delegation Override
When the shared workflow says:
Skill(skill="review-pr", args="...")
Route that to:
- repo-local
.agents/skills/review-pr/SKILL.md - or installed
forge-review-prif the local adapter has been wrapped by the installer
Review Focus for Forge PRs
For Forge repo pull requests, prioritize:
- pipeline state-machine correctness
- nested skill routing correctness
gh/gitcommand correctness- installer side effects and namespace safety
- stale
.claude-only assumptions when Codex-layer files changed - docs and changelog coverage
Keep the shared workflow’s PR creation, auto-merge handoff, and post-merge verification behavior unchanged.
Continuation Rule
Outputting REVIEW_RESULT: does NOT terminate the pipeline. This result block is an intermediate signal for the work-on.md routing loop — not a final answer. After this subcommand completes, control returns to the routing loop in commands/work-on.md, which re-reads GitHub state and dispatches to the next phase (close). Do not treat the result block as a completion signal — the pipeline continues.
© RapierCraftStudios, AGPL-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
Just SKILL.md in .agents/skills/work-on/review of RapierCraftStudios/ForgeDock.
Open the folder on GitHubat commit d89c6f2
Compare with similar skills
Work On 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 |
|---|---|---|---|---|---|---|
| Work On Review this skillRapierCraftStudios/ForgeDock | 117 | — | ~436 | Automated safety check: Pass | AGPL-3.0 | |
| Git Worktree Runnerdyoshikawa/rulesync | 1.5k | — | ~1.3k | Automated safety check: Notes | MIT | |
| Fix Issuenex-agi/NexRL | 119 | — | ~733 | Automated safety check: Pass | Apache-2.0 | |
| Branch Standup Facilitatorthedotmack/claude-mem | 99k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 | |
| Spec Writergarrytan/gstack | 136k | — | ~14k | Automated safety check: Notes | MIT | |
| Project Session ManagerYeachan-Heo/oh-my-claudecode | 40k | — | ~4k | Automated safety check: Pass | MIT |
Similar skills
Fix Issue
nex-agi/NexRL
Fix a GitHub issue using git worktree for isolation. An agent skill from nex-agi/NexRL.
Branch Standup Facilitator
thedotmack/claude-mem
Facilitates a read-only standup between git worktrees, branches or PRs, where each acts as an agent in a shared markdown chat to agree one consolidation plan.
Spec Writer
garrytan/gstack
Converts a vague idea into a precise, executable spec in five phases, files it as an issue and can start an agent on it in a fresh worktree.
Project Session Manager
Yeachan-Heo/oh-my-claudecode
Creates isolated git worktrees, with optional tmux sessions, for PR reviews, issue fixes and feature work across projects and repositories.
Blitz
aiskillstore/marketplace
This skill should be used when parallelizing multi-issue sprints using git worktrees and parallel Claude agents.
More from RapierCraftStudios/ForgeDock
Quality Gate
RapierCraftStudios/ForgeDock
Run a Forge-aware pre-commit quality gate from Codex. An agent skill from RapierCraftStudios/ForgeDock.
ForgeDock PR Review Adapter
RapierCraftStudios/ForgeDock
Adapts a shared pull request review flow to the ForgeDock repository, with its own change categories, shell and installer checks, and optional sub-agent fan-out.
Work On
RapierCraftStudios/ForgeDock
Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.
Forge Issue Investigator
RapierCraftStudios/ForgeDock
Repo adapter that runs the investigation step of the ForgeDock work-on pipeline on a GitHub issue and posts a FORGE:INVESTIGATOR report comment.
Related
Works with
Categories
Questions about Work On Review
What does Work On Review do?
Push a Forge worktree branch, create a PR, and delegate review through the Forge Codex review adapter. Work On Review is an agent skill from RapierCraftStudios/ForgeDock. Push a Forge worktree branch, create a PR, and delegate review through the Forge Codex review adapter.
When should I use Work On Review?
Work On Review fits situations like: tasks that involve Git worktrees.
How do I install Work On Review in Claude Code?
Run `npx skills add RapierCraftStudios/ForgeDock --skill work-on-review -a claude-code`. Or copy the skill folder (.agents/skills/work-on/review in RapierCraftStudios/ForgeDock) into .claude/skills/work-on-review in your project. Claude Code loads it when a task matches its description.
How do I install Work On Review in Codex?
Run `npx skills add RapierCraftStudios/ForgeDock --skill work-on-review -a codex`. Or copy the skill folder (.agents/skills/work-on/review in RapierCraftStudios/ForgeDock) into .agents/skills/work-on-review in your project. Codex loads it when a task matches its description.
Can I use Work On 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 RapierCraftStudios/ForgeDock --skill work-on-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/work-on-review, .gemini/skills/work-on-review, .github/skills/work-on-review and .opencode/skills/work-on-review in your project.
What does Work On Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Work On Review is instructions for the agent only.
Does Work On Review 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 Work On 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 Work On Review use?
Work On Review is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Work On Review use?
About 436 tokens (SKILL.md is roughly 1.7k 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 Work On Review?
Skills that share tags, products or a category with Work On Review: Git Worktree Runner (dyoshikawa/rulesync, 1.5k stars), Fix Issue (nex-agi/NexRL, 119 stars), Branch Standup Facilitator (thedotmack/claude-mem, 99k stars) and Spec Writer (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Work On Review?
RapierCraftStudios (a GitHub organization) maintains it in RapierCraftStudios/ForgeDock, which has 117 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.
Source: RapierCraftStudios/ForgeDock on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.