quality-review

Automates git-based code quality reviews for commits and pull requests.

Updated Jan 25, 2026

Search Tags:#git #quality #standards #lint #code-review #pull-request

Ready to run

npx skills add https://github.com/barikata1984/.agent --skill quality-review-barikata1984

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines and enforces code quality by automatically reviewing changes before they are committed or merged, reducing defects and rework.

Core Features & Use Cases

Automated static analysis checks for linting, style conformance, and common bugs.
Alignment with Issue requirements and project standards to ensure changes meet goals.
Use Case: Before merging a feature branch, run the review to surface issues and guide fixes.

Quick Start

Run the quality-review workflow on your current Git workspace to scan unstaged changes and report issues.

Frequently Asked Questions about quality-review

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

FAQPage Schema

How do I automate code quality checks before a git commit or pull request?▼

To automate code quality checks before a git commit or pull request, you can use automated workflows that parse git diffs and run static analysis. This surfaces linting errors and style conformance issues before changes are merged.

What is the best way to enforce code review standards during development workflows?▼

The best way to enforce code review standards during development workflows is by running automated static analysis on your feature branches. This aligns changes with issue requirements and guides fixes before merging.

Can I use static analyzers and linters to review unstaged changes in my current workspace?▼

Yes, you can use static analyzers and linters to review unstaged changes in your current workspace. Running a quality review workflow scans the active git workspace and generates actionable reports on detected bugs.

How does automated code review parse git diffs to find issues?▼

Automated code review parses git diffs by integrating with git and common linters to extract changed lines. It then applies static analysis checks to these specific changes to identify style violations and common bugs.

Do I need to integrate specific linters to enable automated static analysis for my programming language?▼

Yes, you need to integrate common linters and static analyzers tailored to your programming language. The quality review process depends on these external tools to evaluate code style conformance and detect potential defects.

What issues can automated code quality reviews surface before merging a feature branch?▼

Automated code quality reviews can surface linting errors, style conformance issues, and common bugs before merging a feature branch. This reduces defects and rework by ensuring changes meet project standards and issue requirements.