code-quality-review

Name: code-quality-review
Availability: InStock
Author: Bitsocial

Review code diffs for actionable quality issues before pull requests.

417|25|Updated Aug 25, 2023

Search Tags:#git #diff analysis #code review #pull request #maintainability #test coverage #pre-push

Ready to run

npx skills add https://github.com/bitsocialnet/seedit --skill code-quality-review-bitsocialnet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-quality-review
Source: https://github.com/bitsocialnet/seedit/tree/main/.cursor/skills/code-quality-review
Command: npx skills add https://github.com/bitsocialnet/seedit --skill code-quality-review-bitsocialnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch correctness, maintainability, and scope issues in a code change before it is pushed or opened as a pull request, reducing avoidable rework and review churn.

Core Features & Use Cases

Advisory Diff Review: Examines current branch changes against the right base and surfaces actionable findings only.
Context-Aware Analysis: Reads surrounding source, changed tests, and repo guidance so feedback matches local patterns and documented standards.
Risk-Focused Feedback: Checks for regressions, missing coverage, over-engineering, structure drift, and touched security or performance concerns.
Use Case: A developer can ask for a pre-PR review of AI-generated code to identify brittle logic, missing edge cases, or unnecessary abstractions before merge.

Quick Start

Review the current diff for actionable code quality issues and report only high-confidence suggestions.

Frequently Asked Questions about code-quality-review

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

FAQPage Schema

How do I review a git diff for code quality issues before pushing?▼

To review a git diff before pushing, analyze branch comparisons against master, staged work, or unstaged changes to surface actionable correctness, maintainability, and scope issues. Reading repository guidance, nearby implementation context, and changed tests ensures feedback matches local patterns.

What is the best way to check AI-generated code for missing edge cases before a pull request?▼

Checking AI-generated code for missing edge cases requires a pre-merge advisory pass that reads touched paths and surrounding source. This risk-focused analysis identifies brittle logic, unnecessary abstractions, and missing verification coverage before you open a pull request.

How do I run a pre-push code review on staged or unstaged work?▼

Running a pre-push code review on staged or unstaged work involves examining the current diff against the correct base branch. The process surfaces only high-confidence findings related to regressions, structure drift, and touched security or performance concerns.

Can I assess test coverage and security risks from a branch diff against master?▼

Yes, you can assess test coverage and security risks from a branch diff against master by reading changed tests and touched paths. This context-aware analysis evaluates verification coverage and highlights specific security or performance regressions introduced by the changes.

When should I use an advisory code review instead of a standard pull request review?▼

Use an advisory code review before pushing or opening a pull request to reduce avoidable rework and review churn. It is specifically suited for catching over-engineering and scope issues in AI-generated changes or branch comparisons prior to the standard merge process.