review-local

Review uncommitted git changes for bugs, quality, and test coverage.

Updated Oct 8, 2024

Search Tags:#code quality #code review #test coverage #bug detection #git repository

Ready to run

npx skills add https://github.com/gerardovitale/travel-assistant --skill review-local-gerardovitale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-local
Source: https://github.com/gerardovitale/travel-assistant/tree/main/.agents/skills/review-local
Command: npx skills add https://github.com/gerardovitale/travel-assistant --skill review-local-gerardovitale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the code review process by identifying bugs, improvements, and potential issues in uncommitted changes, helping maintain code quality and prevent regressions.

Core Features & Use Cases

Bug Detection: Identify logic errors, type mismatches, and security vulnerabilities.
Code Quality: Check for naming conventions, dead code, and performance bottlenecks.
Test Coverage: Ensure functions and classes are tested and flag untested code paths.
Use Case: When reviewing code without a Pull Request, use this Skill to perform a thorough review of all uncommitted changes directly in the working tree.

Quick Start

Run the 'review-local' skill to automatically review all uncommitted changes in the repository.

Frequently Asked Questions about review-local

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

FAQPage Schema

How do I review uncommitted code changes for bugs without creating a pull request?▼

Review uncommitted code changes directly in the working tree to analyze the git repository for bugs, code quality issues, and test coverage gaps without requiring a pull request.

Can I check for test coverage gaps in my local working tree before committing?▼

Yes, checking for test coverage gaps in the local working tree ensures functions and classes are tested, flagging untested code paths before you commit changes.

What is the best way to detect security vulnerabilities and dead code in uncommitted git changes?▼

Detecting security vulnerabilities and dead code in uncommitted git changes involves analyzing the repository working tree to identify logic errors, type mismatches, and performance bottlenecks.

Does local code review require command-line tools to run on a git repository?▼

Yes, local code review requires execution of specific command-line tools within the git repository to thoroughly analyze uncommitted changes for bugs and quality issues.

How do I check naming conventions and code quality issues in uncommitted changes?▼

Checking naming conventions and code quality issues in uncommitted changes requires analyzing the working tree to identify dead code, performance bottlenecks, and potential regressions.