Menu
Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run a Forge-aware pre-commit quality gate from Codex.
Review Forge pull requests from Codex with Forge-aware heuristics and the shared Forge verdict/merge model.
Investigate a Forge GitHub issue from Codex and post a FORGE:INVESTIGATOR report.
Push a Forge worktree branch, create a PR, and delegate review through the Forge Codex review adapter.
Build a Forge issue from Codex using Codex-native worktrees and Forge-aware subcommand routing.
Validate Forge build changes from Codex with Forge-aware quality gate and installer checks.
| name | work-on |
| description | Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex. |
Use commands/work-on.md as the authoritative state-machine source, but apply the Forge repo overrides below when running from Codex in this repository.
Inside the Forge repo, resolve issue targets like this unless the user explicitly prefixes another project:
| Input | Repo |
|---|---|
123, #123, next, empty | RapierCraftStudios/forgedock |
forge:123 | RapierCraftStudios/forgedock |
Satellite prefixes (e.g. mcp:5, sdk:12) are project-specific and defined in forge.yaml → repos.satellites. See commands/work-on.md Phase 0B for multi-repo routing.
For Forge repo issues, set:
GH_REPO=RapierCraftStudios/forgedockGH_FLAG=--repo RapierCraftStudios/forgedockREPO_PATH=/home/mrdubey/projects/forgedockSTAGING_BRANCH=stagingDEFAULT_BRANCH=main.claude/worktrees/... example path in the shared command spec as .codex/worktrees/... for Codex execution in this repo./home/mrdubey/projects/forgedock/.codex/worktrees.gh api repos/{GH_REPO}/issues/{NUMBER}/comments for comment reads instead of gh issue view --comments.workflow:* labels on demand if the Forge repo does not already have them.When the shared workflow says to inspect domain files, prioritize Forge repo files instead:
commands/**/*.mddocs/**/*.mdscripts/**/*.shinstall.sh, install-codex.sh, update.shAGENTS.md, CLAUDE.md, CHANGELOG.md.agents/skills/**/*.mdWhen commands/work-on.md invokes nested skills, use these Codex adapters:
work-on:investigate -> repo-local .agents/skills/work-on/investigate/SKILL.mdwork-on:build -> repo-local .agents/skills/work-on/build/SKILL.mdwork-on:review -> repo-local .agents/skills/work-on/review/SKILL.mdwork-on:close -> installed forge-work-on-closework-on:decompose -> installed forge-work-on-decomposeIf an installed forge-* skill exists for the nested command, use it. Otherwise read the referenced shared command file directly and continue manually.
Preserve the shared Forge behavior from commands/work-on.md: GitHub state is the memory layer, FORGE:* comments remain machine-readable, and the routing loop continues until an explicit terminal condition is reached.