code-critique

Analyze code for quality issues with line numbers and severity scores.

4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/mgd34msu/goodvibes-gemini --skill code-critique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-critique
Source: https://github.com/mgd34msu/goodvibes-gemini/tree/main/skills/code-critique
Command: npx skills add https://github.com/mgd34msu/goodvibes-gemini --skill code-critique

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies, categorizes, and articulates code issues with extreme precision and quantifiable evidence, ensuring code quality meets the highest standards.

Core Features & Use Cases

  • Comprehensive Audits: Performs detailed reviews covering structural integrity, naming conventions, logic flaws, performance bottlenecks, security vulnerabilities, and style consistency.
  • Quantifiable Feedback: Provides specific line numbers, severity scores, and impact assessments for every identified issue.
  • Use Case: Before merging a critical feature, use this Skill to perform a pre-PR audit. It will flag every potential issue, from SQL injection risks to vague variable names, with clear severity ratings and actionable fixes.

Quick Start

Perform a brutally honest code critique of the provided code snippet.

Frequently Asked Questions about code-critique

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

FAQPage Schema
How do I perform an automated code quality audit before merging a pull request?

To perform a code quality audit, submit your code snippet for analysis. The tool evaluates security vulnerabilities, logic flaws, performance bottlenecks, and style consistency, returning specific line numbers, severity scores, and impact assessments for actionable refactoring.

What is the best way to identify security vulnerabilities and performance bottlenecks in my source code?

Identifying security vulnerabilities and performance bottlenecks requires a comprehensive structural review. This process analyzes your code to detect SQL injection risks and execution inefficiencies, providing quantified severity scores and direct feedback for each issue found.

How does a quantified code review mechanism work for evaluating structural integrity and naming conventions?

A quantified code review mechanism works by parsing your code to categorize structural integrity and naming violations. It articulates issues with extreme precision, assigning severity scores and specific line numbers to ensure quality meets the highest standards.

Can I use this code critique approach for any programming language or specific scripts only?

You can use this code critique approach to analyze any provided code snippet. It evaluates logic flaws, style consistency, and structural issues regardless of language, adhering to strict communication patterns to deliver direct and actionable critique.

What are the limitations of using automated severity scores for code refactoring?

The limitation of using automated severity scores for code refactoring is that the assessment is brutally honest but strictly syntax and logic based. It flags specific violations and impact assessments but requires human judgment to implement the recommended fixes.

Why does my code review audit return vague variable names as critical severity issues?

Your code review audit returns vague variable names as critical severity issues because the assessment categorizes naming convention violations with quantified impact scores. It flags every potential issue with clear severity ratings to ensure strict structural integrity and style consistency.