local-code-review

Identify and report issues from git diffs for Databao CLI code changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JetBrains/databao-cli --skill local-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-code-review
Source: https://github.com/JetBrains/databao-cli/tree/main/.claude/skills/local-code-review
Command: npx skills add https://github.com/JetBrains/databao-cli --skill local-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review local code changes for Databao CLI with NO prior context to identify correctness, regressions, missing tests, and Databao-specific risks.

Core Features & Use Cases

  • Provide a rapid, findings-first review of diffs by reading diffs, surrounding implementation, and related tests.
  • Prioritize issues that affect CLI/API/UI behavior, provider wiring, configuration/build flows, and test coverage.
  • Use cases include pre-merge diffs on feature branches, staged changes, or targeted file reviews to surface critical defects before integration.

Quick Start

Run the current branch diff to surface findings before merging.

Frequently Asked Questions about local-code-review

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

FAQPage Schema
How do I review git diffs for CLI behavior issues before merging?

Review git diffs for CLI behavior issues by analyzing branch diffs against main, staged changes, or file paths to identify regressions and wiring defects. This non-mutating analysis references concrete file and line numbers to present findings first without editing files.

What is the best way to find missing tests in staged code changes?

The best way to find missing tests in staged code changes is to run a findings-first review that reads surrounding implementation and related tests. This identifies test coverage gaps by analyzing staged diffs and surfacing critical defects before integration.

Can I check provider wiring and configuration risks in a feature branch diff?

Yes, you can check provider wiring and configuration risks in a feature branch diff. The analysis prioritizes issues affecting provider wiring, configuration flows, and build processes by reading the diff and surrounding implementation to report concrete findings.

Does local code review work with files:path targeting instead of full branch diffs?

Local code review works with files:path targeting, branch diffs against main, and staged changes. It requires non-mutating analysis to surface correctness issues and Databao-specific risks, referencing concrete file and line locations in the output.

How do I surface correctness issues in code changes without modifying files?

Surface correctness issues in code changes without modifying files by performing a non-mutating analysis of git diffs. The review identifies regressions and Databao-specific risks, presenting findings first with concrete file and line references while indicating open questions.

When do I need a findings-first diff review for Databao CLI code?

You need a findings-first diff review for Databao CLI code when checking pre-merge feature branches, staged changes, or targeted file reviews. It surfaces critical defects affecting CLI behavior and test coverage before integration without prior context.