grumpy-review

Review code for bugs in error paths, resource lifecycles, and concurrency.

Updated Sep 9, 2024
One-click install
npx skills add https://github.com/axel-kaliff/dotfiles --skill grumpy-review-axel-kaliff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grumpy-review
Source: https://github.com/axel-kaliff/dotfiles/tree/main/claude/.claude/skills/grumpy-review
Command: npx skills add https://github.com/axel-kaliff/dotfiles --skill grumpy-review-axel-kaliff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers identify real bugs in code by applying a grumpy systems-engineering perspective to detect errors, resource leaks, race conditions, and implicit assumptions, rather than performing a style review.

Core Features & Use Cases

  • Targeted reviews: Accepts a file or directory path or auto-detects changes to review the most relevant code.
  • Comprehensive bug-hunting: Focuses on correctness, resource lifecycles, and concurrency issues, delivering actionable findings.
  • Structured verdicts: Returns a severity-labeled report with exact line references for fast remediation.

Quick Start

Provide a file or directory path to analyze, or run with no argument to auto-detect changes

Frequently Asked Questions about grumpy-review

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

FAQPage Schema
How do I find race conditions and resource leaks in my code?

To find race conditions and resource leaks, this Skill simulates a grumpy systems-engineer code review that targets error paths, resource lifecycles, and concurrency issues, returning a structured verdict with severity tags and exact line references.

Can I run an automated bug detection review on a specific directory path?

You can run automated bug detection on a specific directory path by providing it as an argument, or by running the Skill with no argument to auto-detect recent changes and review the most relevant code.

Does this code review tool check for real bugs or just code style?

This code review tool checks for real bugs by focusing on correctness, resource lifecycles, and implicit assumptions, deliberately avoiding standard style checks to prioritize actionable systems-engineering findings.

What's the best way to review a diff for concurrency issues?

The best way to review a diff for concurrency issues is to use a targeted bug-hunting review that applies a systems-engineering perspective to your changes, delivering a severity-labeled report with exact line references for fast remediation.

How are the detected bugs reported in the code review verdict?

Detected bugs are reported in a structured verdict that includes severity tags and exact line references, allowing you to quickly locate and remediate errors, race conditions, and resource leaks across the target code.