Menu
Investigate a Forge GitHub issue from Codex and post a FORGE:INVESTIGATOR report.
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.
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.
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-investigate |
| description | Investigate a Forge GitHub issue from Codex and post a FORGE:INVESTIGATOR report. |
Use commands/work-on/investigate.md as the authoritative investigation workflow, with these Forge repo overrides:
RapierCraftStudios/forgedock.gh api repos/RapierCraftStudios/forgedock/issues/{NUMBER}/comments.FORGE:* markers as the primary resume protocol.Prioritize these files when the issue is in the Forge repo:
commands/work-on.mdcommands/review-pr.mdcommands/quality-gate.mdcommands/orchestrate.mdcommands/milestone.mdinstall.sh, install-codex.shAGENTS.md, CLAUDE.md, docs/CODEX.md, docs/WORKFLOW.mdcommands/, docs/, scripts/, or .agents/skills/If the shared command’s domain table references project-specific paths that are not relevant to this repo, replace it with the Forge repo file set above and continue with the same output contract: post a <!-- FORGE:INVESTIGATOR --> comment, update labels best-effort, and return the structured investigate result.
Outputting INVESTIGATE_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 (build, decompose, or INVALID stop). Do not treat the result block as a completion signal — the pipeline continues.