DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to review a branch before merge and get a shareable HTML report with Codexqa

Produce a bilingual REVIEW-REPORT.html with merge risk, call chains, and test gaps for a reviewer.

Who it is forA developer or tech lead who has an AI-generated branch ready and needs a reviewer-ready report before the merge gate.

The problemA raw git diff does not show call chains, blast radius, or which tests are missing, so reviewers miss risk.

The outcomeA REVIEW-REPORT.html on disk that lists merge risk, gaps, and what still needs tests, ready to attach to the review.

What you need first

  • One of Cursor, Claude Code, Codex, or OpenClaw installed
  • A local git repository with the branch to check (the README refers to origin/main)
  • Node.js with npx available (inferred from the npx install commands)
  • For browser replay: Playwright Chromium, as named in the README

Steps

  1. Install the code reviewer skill with npx skills add openqa-cn/codexqa --skill codexqa-code-reviewer.
  2. Pick your agent (Cursor, Claude Code, Codex, or OpenClaw) when prompted.
  3. Check out the branch you want to review in your local repository.
  4. Open a new agent session and paste the agent prompt below.
  5. Open the generated REVIEW-REPORT.html and attach it to the review request.

Prompt for your agent

Use the codexqa-code-reviewer skill in this repo to review the current branch against origin/main. Collect the CodexQA evidence pack (callers, blast radius, test edges) and write a bilingual REVIEW-REPORT.html. Verify that the report lists merge risk and the test gaps it found.

Caveat. The README says the agent you already use is the runtime, so report quality depends on the model behind that agent, and the README gives no benchmark for the reviewer skill.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page