pre-review

Analyze git diffs to detect critical issues and test coverage gaps.

164|44|Updated Jun 30, 2023
One-click install
npx skills add https://github.com/hivemq/hivemq-edge --skill pre-review-hivemq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-review
Source: https://github.com/hivemq/hivemq-edge/tree/main/hivemq-edge-frontend/.claude/skills/pre-review
Command: npx skills add https://github.com/hivemq/hivemq-edge --skill pre-review-hivemq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated pre-merge code review that analyzes changes in the current branch to catch patterns, quality gaps, and potential issues before PR submission.

Core Features & Use Cases

  • Change analysis: Detects modified files, counts lines changed, and identifies test vs non-test changes to surface risk areas.
  • Quality gates: Flags critical issues (must fix) and pattern violations (should fix) with actionable recommendations.
  • Reporting: Generates a comprehensive report outlining findings, suggested fixes, and potential gains in test coverage.
  • Use Case: Use this during PR workflows to ensure new code adheres to project standards before submission.

Quick Start

Run the pre-review command to analyze the current branch and receive a structured report.

Frequently Asked Questions about pre-review

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

FAQPage Schema
How do I automate code review for pull requests in JavaScript repositories?

Automated code review for pull requests analyzes your current git diff to catch pattern violations, test coverage gaps, and critical issues before PR submission. It distinguishes source changes from tests and generated files to produce targeted actionable reports.

What is pre-merge code quality analysis and how does it work?

Pre-merge code quality analysis evaluates git diffs to identify must-fix critical issues and should-fix pattern violations. It parses modified files, counts changed lines, and separates test files from source files to surface risk areas before merging.

Can I configure quality gates to focus on specific files or sections in a PR?

Yes, you can configure quality gates with options for base branch, focus areas, and sections to skip. This ensures the automated pre-merge analysis targets specific patterns and test coverage requirements relevant to your JavaScript or TypeScript workflow.

Does automated PR review detect missing test coverage for new code changes?

Yes, automated PR review detects test coverage gaps by distinguishing test changes from non-test source modifications. It analyzes the git diff to flag new code lacking corresponding tests and suggests potential coverage gains in the generated report.

What's the best way to catch pattern violations before creating a pull request?

The best way to catch pattern violations before creating a PR is running deterministic diff analysis with linting and parsing utilities. This identifies must-fix issues and should-fix violations, generating a comprehensive report with actionable fix recommendations.

When should I not use automated git diff analysis for code review?

Automated git diff analysis is not suited for repositories outside JavaScript and TypeScript ecosystems or for evaluating architectural design decisions. It focuses on deterministic pattern matching, linting, and test coverage gaps rather than subjective code review.