review-helper

Analyze codebases to identify bugs, risks, regressions, and missing tests.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/jibaxZZZ/codex-root-configuration --skill review-helper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-helper
Source: https://github.com/jibaxZZZ/codex-root-configuration/tree/main/.codex/skills/review-helper
Command: npx skills add https://github.com/jibaxZZZ/codex-root-configuration --skill review-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often miss bugs, risks, regressions, and missing tests, slowing delivery and increasing risk. This Skill identifies these issues and provides actionable findings to improve code quality.

Core Features & Use Cases

  • Automated bug detection: highlights defects and potential risk areas across changed files.
  • Risk and regression assessment: flags areas with high likelihood of regressions and safety concerns.
  • Missing tests guidance: points out untested paths and suggests test coverage improvements.
  • Actionable output: lists impacted files and specific references to facilitate quick remediation.
  • Use Case: during a PR review, run this Skill to surface bugs, risky changes, and missing tests before merge.

Quick Start

Review the latest pull request to surface bugs, risks, regressions, and missing tests.

Frequently Asked Questions about review-helper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find bugs and regressions in a pull request before merging?

To find bugs and regressions in a pull request, you can analyze changed files to highlight defects, assess safety risks, and produce actionable findings with specific file references and severity levels.

Can I detect missing tests across multiple languages during code review?

Yes, you can detect missing tests across multiple languages during code review by analyzing codebases to flag untested paths and suggest test coverage improvements before merging changes.

What is the best way to integrate automated risk assessment into CI workflows?

Integrating risk assessment into CI workflows involves analyzing pull requests to flag high-risk areas and regressions, delivering actionable output with severity levels and impacted file references for quick remediation.

Does static analysis of codebases work for highlighting potential risk areas?

Static analysis of codebases works for highlighting potential risk areas by assessing changes for defects and safety concerns, then outputting severity levels and affected file references.

How do I surface untested paths and suggest test coverage improvements in a PR?

You surface untested paths and suggest test coverage improvements by running automated analysis on the codebase during a PR review to identify where tests are absent and guide coverage additions.

What actionable output does automated bug detection provide for changed files?

Automated bug detection provides actionable output for changed files by listing impacted files, specific code references, and severity levels to facilitate quick remediation of defects and regressions.