Menu
Build a Forge issue from Codex using Codex-native worktrees and Forge-aware subcommand routing.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.
Validate Forge build changes from Codex with Forge-aware quality gate and installer checks.
| name | work-on-build |
| description | Build a Forge issue from Codex using Codex-native worktrees and Forge-aware subcommand routing. |
Use commands/work-on/build.md as the authoritative build-phase workflow, with these Forge repo overrides:
RapierCraftStudios/forge..claude/worktrees/... path assumption to /home/mrdubey/projects/forge/.codex/worktrees/..../home/mrdubey/projects/forge/.codex/worktrees exists before creating worktrees.Use these adapters when the shared workflow invokes nested skills:
work-on:build:context -> installed forge-work-on-build-contextwork-on:build:architect -> installed forge-work-on-build-architectwork-on:build:implement -> installed forge-work-on-build-implementwork-on:build:validate -> repo-local .agents/skills/work-on/build/validate/SKILL.mdquality-gate -> repo-local .agents/skills/quality-gate/SKILL.mdFor Forge issues, expected deliverables usually live in:
commands/**/*.md.agents/skills/**/*.mddocs/**/*.mdscripts/**/*.shinstall.sh, install-codex.sh, AGENTS.md, CLAUDE.md, CHANGELOG.mdPreserve the shared builder contract, context, architect, implement, and validate sequencing from commands/work-on/build.md. Only the repo defaults, worktree root, and nested-skill mapping change here.
Outputting BUILD_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 (review). Do not treat the result block as a completion signal — the pipeline continues.