Menu
Run a Forge-aware pre-commit quality gate 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
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.
Validate Forge build changes from Codex with Forge-aware quality gate and installer checks.
| name | quality-gate |
| description | Run a Forge-aware pre-commit quality gate from Codex. |
Use commands/quality-gate.md as the source for gate semantics and PASS/FAIL behavior, but replace app-specific domain checks with Forge repo checks when the changed files belong to this repository.
Classify changed files like this:
commands/**/*.md -> COMMANDS.agents/skills/**/*.md -> SKILLSdocs/**/*.md, AGENTS.md, CLAUDE.md, CHANGELOG.md -> DOCSinstall*.sh, scripts/**/*.sh, update.sh -> SHELLAlways include CONSISTENCY for Forge repo changes.
.claude/commands, .claude/worktrees, or deleted file referencesSkill("...") references still map cleanly to forge-* adapters or repo-local skillsFORGE:* comments, or routing-loop continuationbash -n on every changed shell scriptCHANGELOG.md was updatedAGENTS.md and docs/CODEX.md remain alignedReturn PASS only when the changed Forge files are internally consistent, shell scripts parse, and no high-severity workflow regression is visible from the diff.
Keep the shared quality-gate contract: HIGH/MEDIUM findings are blocking, LOW findings are advisory.