Menu
Validate Forge build changes from Codex with Forge-aware quality gate and installer checks.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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.
Build a Forge issue from Codex using Codex-native worktrees and Forge-aware subcommand routing.
| name | work-on-build-validate |
| description | Validate Forge build changes from Codex with Forge-aware quality gate and installer checks. |
Use commands/work-on/build/validate.md for gate-loop semantics, but apply these Forge repo overrides when the changed files are in this repository:
Skill("quality-gate"), use the repo-local Forge adapter at .agents/skills/quality-gate/SKILL.md or the installed forge-quality-gate skill.GATE_PASSED contract unchanged.For Forge repo changes:
bash -n on every changed *.sh file.install-codex.sh changed, always run bash -n install-codex.sh.install.sh changed, always run bash -n install.sh.AGENTS.md, docs/CODEX.md, .agents/skills/**, install-codex.sh), verify naming/path consistency against commands/**/*.md.CHANGELOG.md was updated.If the changed files are only Markdown/docs/skill files with no executable shell changes, skip language-specific format/build steps from the shared workflow and treat the quality gate plus reference consistency checks as the required validation surface.
Return the same structured VALIDATE_RESULT block expected by the shared workflow.