code-review

Name: code-review
Availability: InStock
Author: LinoWhy

Automate code review to identify correctness issues and regression risks.

Updated Aug 17, 2024

Search Tags:#quality #review #regression #patch #code-review #risk #pull-request

Ready to run

npx skills add https://github.com/LinoWhy/.dotfiles --skill code-review-linowhy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/LinoWhy/.dotfiles/tree/main/agents/.agents/local-skills/code-review
Command: npx skills add https://github.com/LinoWhy/.dotfiles --skill code-review-linowhy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates strict code reviews to identify correctness issues, potential regressions, and gaps in validation in commits, patches, or PRs.

Core Features & Use Cases

Automated correctness checks: Identify logic errors, edge-case failures, and potential regressions in proposed changes.
Regression risk prioritization: Rank findings by impact and likelihood to help reviewers focus on critical areas.
Actionable remediation guidance: Suggest concrete fixes and verification steps to close gaps.

Quick Start

Describe the patch or commit details and request a strict, prioritized code-review assessment.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I automate code review to identify correctness issues in a pull request?▼

You can automate code review by describing the commit or pull request details to receive a strict assessment that detects logic errors, edge-case failures, and missing validations, generating prioritized findings with actionable remediation guidance.

What is regression risk prioritization and how does it help reviewers focus?▼

Regression risk prioritization evaluates proposed code changes to rank potential regressions by impact and likelihood, helping reviewers focus immediately on the most critical correctness issues and remediation steps.

Can I use this to review patches and commits across different repositories?▼

Yes, you can review patches and commits across different repositories by providing the described changes, which the code review process evaluates for correctness issues and regression risks regardless of the specific repository context.

What's the best way to check for missing validations in a described code change?▼

The best way to check for missing validations is to request a strict code review assessment of the described change, which automatically identifies gaps in validation and provides actionable remediation guidance to close them.

Does the code review provide actionable remediation guidance for identified issues?▼

Yes, the code review provides actionable remediation guidance by suggesting concrete fixes and verification steps to close validation gaps and resolve identified correctness issues and regression risks.

When do I need to provide described changes instead of a direct pull request for code review?▼

You need to provide described changes when a direct pull request is unavailable, allowing the code review to still analyze the patch details for correctness issues, regression risks, and missing validations with prioritized findings.