DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to check a Codex Guard install for config errors with Codex Guard

Run the read-only doctor to find workflow, permission and policy mistakes locally.

Who it is forA maintainer who just installed or edited Codex Guard policy and is unsure whether the workflow is correct.

The problemA missing permission or a typo in the policy file can quietly weaken or break the gate.

The outcomeA list of checks for the PR trigger, Action step, permissions, preset, policy YAML and fail-on values, with a clear exit code.

What you need first

  • A GitHub repository with Actions enabled and permission to add a workflow file
  • Node.js with npx available on your machine
  • A Git working copy of the repository (the init command runs from its root)
  • Permission to change branch protection settings if you want the check to block merges

Steps

  1. Run npx --yes codex-guard doctor from the repository root.
  2. Run npx --yes codex-guard doctor --json if you need machine-readable output.
  3. Fix any configuration errors in the workflow or .github/codex-guard.yml.
  4. Run the doctor again until it exits 0.

Prompt for your agent

In the repository at <repo-path>, run `npx --yes codex-guard doctor --json` and save the output. Expected output: JSON describing each check as a pass, warning or error. Verify that the command exit code is 0 or 1 and that any error names the file and key involved.

Caveat. The doctor only reads local files, so GitHub branch protection and organization policy still need to be checked in repository settings.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for Akimiya-z/codex-guard and "Check a Codex Guard install for config errors"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer