This repository also configures its own agents. See what claude-codex-forge tells them →
Command Claude Code
Use after the PR is approved. This workflow merges only with explicit human authorization, preserves developer continuity, and removes the feature worktree without choosing a permanent engine.
Command Claude Code
Diagnose and fix a reproducible defect through an open PR. The active Claude Code or Codex host is the main agent for this session; there is no permanent main engine.
Command Claude Code
Build a substantial feature from requirements through an open PR. The active Claude Code or Codex host is the main agent for this session; there is no permanent main engine.
Command Claude Code
Use only for a clearly understood, low-risk, non-user-facing change with an obvious focused check. The change may touch at most three implementation paths; exact release metadata paths README.md and docs/CHANGELOG.md do not consume that budget. If diagnosis is uncertain, architecture or product judgment is needed, the…
Command Claude Code
Use after a PR receives automated or human feedback. The active Claude Code or Codex host remains the main agent for this session; reviewer choice is independent.
Command Claude Code
This canonical workflow is installed only as .forge/workflows/goal.md. Forge must never install .claude/commands/goal.md or .agents/skills/goal/SKILL.md; each host retains its native /goal.
Command Claude Code needs its repo
Use the fixed-target compatibility launcher registered by the active Claude Code or Codex adapter. It declares the current host to the dispatcher; mainhost is routing metadata, not authenticated session identity or reviewer evidence. Never invent a main engine flag. User-facing reviewer choices map only to --engine…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: