# AI use cases for Openqodex (openqodex/openqodex) Repo: [openqodex/openqodex](https://github.com/openqodex/openqodex) | Use cases: 4 | Page: https://dedupedai.com/use-cases/openqodex-openqodex/ OpenQodex is an open source tool that reviews your code change before you push, combining scanners with a separate AI reviewer that uses your own Claude Code or Codex login. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Try OpenQodex on a demo repo with planted bugs: https://dedupedai.com/use-cases/openqodex-openqodex/try-openqodex-on-demo-repo/ - Review your change before you push it: https://dedupedai.com/use-cases/openqodex-openqodex/review-change-before-push/ - Review a pull request on your machine before merging: https://dedupedai.com/use-cases/openqodex-openqodex/review-pull-request-locally/ - Add a GitHub scanner to your review after approval: https://dedupedai.com/use-cases/openqodex-openqodex/add-custom-scanner-from-github/ ## How to try OpenQodex on a demo repo with planted bugs with Openqodex Repo: [openqodex/openqodex](https://github.com/openqodex/openqodex) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Run a built-in demo that scans a small repository seeded with bugs, to see the output first. **Who it is for:** A developer or team lead who wants to see what OpenQodex catches before adding it to a real project. **The problem:** It is hard to judge a review tool from its description alone, and trying it on real code risks noise or setup work. **The outcome:** You see scanner findings and report output on a known repository, so you know what a review looks like. ### Steps 1. Make sure Node 22 or newer and git are installed. 2. Run `npx openqodex demo`. 3. Read the printed receipt and the findings it lists. 4. Open the report file the demo names to see the full output. ### Prompt to paste into your agent ```text In the repo at , run `npx openqodex demo` and report the verdict and the number of findings printed in the receipt. Verify that a report file path is printed at the end. ``` ### Caveat The demo scans a planted-bug repository, so its findings show the tool working, not how it performs on your code. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/openqodex-openqodex/try-openqodex-on-demo-repo/ ## How to review your change before you push it with Openqodex Repo: [openqodex/openqodex](https://github.com/openqodex/openqodex) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run a review of unpushed commits and uncommitted work, then choose which findings to fix. **Who it is for:** A developer using Claude Code, Codex, Cursor or Cline who wants a check before code leaves the machine. **The problem:** Problems such as leaked secrets or risky code often reach the remote because nobody checked the change before the push. **The outcome:** Your change gets scanner checks and an independent AI review, and you decide which findings your agent fixes. ### Steps 1. Run `npx openqodex init` in your repository terminal and answer the one question it asks. 2. Ask your agent: "review my change with Openqodex", or run `~/.openqodex/bin/openqodex review` in your own terminal. 3. Read the receipt and open the path of report.html that it prints. 4. Reply to your agent with "Fix all" or name the findings to fix. ### Prompt to paste into your agent ```text In the repo at , run `~/.openqodex/bin/openqodex review` and show me the receipt verdict and each finding line. Verify that the output ends with a report.html path or a 'Review incomplete' message with the missing stages named. ``` ### Caveat A full review needs Claude Code or Codex installed and logged in, and it sends your change to that login's model service. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/openqodex-openqodex/review-change-before-push/ ## How to review a pull request on your machine before merging with Openqodex Repo: [openqodex/openqodex](https://github.com/openqodex/openqodex) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run a full OpenQodex review on a pull request number from your own terminal. **Who it is for:** A reviewer who wants a second check on a pull request before approving it. **The problem:** Reading a large pull request by hand misses problems that scanners and a second reviewer can catch. **The outcome:** You get a review report for that pull request, with each stage named if it did not run. ### Steps 1. Install OpenQodex in the repository with `npx openqodex init`. 2. Run `~/.openqodex/bin/openqodex review '#'`, replacing with the pull request number. (inferred, check the README) 3. Read the receipt and open the report.html path it prints. 4. If the output says "Review incomplete", note the missing stage it lists before you rely on the result. ### Prompt to paste into your agent ```text In the repo at , review pull request with OpenQodex and summarize the verdict and each finding. Verify that the output either names a report path or lists the stages that did not run. ``` ### Caveat The pull request review is run from your machine, so it depends on Claude Code or Codex being logged in for the full review. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/openqodex-openqodex/review-pull-request-locally/ ## How to add a GitHub scanner to your review after approval with Openqodex Repo: [openqodex/openqodex](https://github.com/openqodex/openqodex) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Configure a compatible scanner from GitHub, approve it, and run it in your reviews. **Who it is for:** A security-minded developer who wants a scanner beyond the 22 built-in ones in one repository. **The problem:** The built-in scanners may not cover a check your team needs, and adding one safely takes care. **The outcome:** The scanner runs in your next review only after you approve its exact entry. ### Steps 1. Add the scanner under `scanners` and `custom` in `.openqodex/config.yaml`, with its source, run command and target. 2. Run `npx openqodex trust` and answer yes only after you read what it will run. 3. Run `npx openqodex scan --only custom:bearer` to see the scanner work. 4. Run a review, and confirm the custom scanner's findings appear in the output. ### Prompt to paste into your agent ```text In the repo at , add the Bearer scanner from https://github.com/Bearer/bearer as a custom scanner in .openqodex/config.yaml. Do not run `openqodex trust` until I approve; then run `npx openqodex scan --only custom:bearer` and report whether it produced findings. ``` ### Caveat The Bearer CLI is under the Elastic License 2.0, which is not an open source licence, and a fresh GitHub-hosted runner skips approved custom scanners. Risk, remote script: The trust step downloads a release asset and then runs its command on your machine, so read the shown command before answering yes. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/openqodex-openqodex/add-custom-scanner-from-github/