Gate agent code changes with OpenQodex review
Run diff-aware scanner and AI review gates before pushing Claude Code or Codex changes, with pinned scanners, isolated reviewer contexts, and optional pre-push enforcement.
npx skills add agentskillexchange/skills --skill gate-agent-code-changes-with-openqodex-review
npx openqodex init for terminal setup, or install the agent skill with npx skills add openqodex/openqodex; then run or ask the agent to run openqodex review against the current change before pushing.Use OpenQodex when an operator wants a coding agent or terminal workflow to review the current change before it is pushed. The workflow is to initialize OpenQodex, let it identify unpushed commits and working-tree changes, run targeted scanners for SAST, secrets, dependencies, lint, and related findings, then hand every changed line and scanner result to a separate Claude Code or Codex reviewer process for a verdict. Invoke this instead of relying on the coding product’s normal chat review when a team needs a repeatable local gate, scanner-backed findings, an optional pre-push hook, and review records tied to the exact diff. The scope boundary is pre-push code review for local changes; it is not a generic SAST catalog entry, CI platform, MCP server, or full application-security program.
What this skill actually does
Inputs and prerequisites: Node/npm, Git, OpenQodex CLI, Claude Code or Codex for full reviewer mode, scanner runtimes as needed by project language.
Setup notes: Run npx openqodex init for terminal setup, or install the agent skill with npx skills add openqodex/openqodex ; then run or ask the agent to run openqodex review against the current change before pushing.
Source and verification boundary: use https://qodex.ai/openqodex as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.