skills.rest
habit-hooks
habit-hooksOFFICIAL
Explore all skills by this author →
GitHub

habit-hooks-review

Detects hidden correctness bugs, design flaws, and missing test coverage in change sets after linting passes.

40|1|Updated May 26, 2026
Search Tags:#static analysis#code review#linting#software quality#quality gate#change validation#habit-hooks
One-click install
npx skills add https://github.com/habit-hooks/habit-hooks --skill habit-hooks-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: habit-hooks-review
Source: https://github.com/habit-hooks/habit-hooks/tree/main/skills/habit-hooks-review
Command: npx skills add https://github.com/habit-hooks/habit-hooks --skill habit-hooks-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated linting tools like habit-hooks catch structural code smells but miss critical quality issues such as correctness bugs, design flaws, missing test coverage, and edge case oversights that can cause production failures even after a clean lint run.

Core Features & Use Cases

  • Dedicated Sub-Agent Review: Spawns an unbiased reviewer sub-agent to perform a fresh read of your change set, avoiding the blind spots of the implementing agent.
  • Comprehensive Quality Check: Evaluates changes for correctness, design quality, test coverage, edge case handling, and naming clarity that static analysis tools cannot detect.
  • Structured Verdict & Categorization: Returns a clear PASS/CHANGES NEEDED verdict, with findings sorted by severity (blocking, worth flagging, nits) and required gate check results.
  • Use Case: After finishing a feature or bug fix and confirming habit-hooks reports no structural issues, use this skill to get a second-pass review to catch hidden flaws before merging your code.

Quick Start

Invoke the habit-hooks-review skill to assess your recent code changes for hidden correctness bugs, design issues, and test gaps immediately after habit-hooks reports a clean run.

Frequently Asked Questions about habit-hooks-review

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

FAQPage Schema
How do I catch correctness bugs that pass static analysis linting?▼

A post-lint code review provides a secondary quality gate that scans change sets for hidden correctness bugs, edge case oversights, and design flaws. It catches quality issues that structural linting tools miss before you merge finished features or bug fixes.

Why does my code pass linting checks but still have design flaws?▼

Code passes linting but still has design flaws because static analysis tools only catch structural code smells. A dedicated post-lint review is needed to detect correctness issues, missing test coverage, and edge case oversights that automated linters cannot understand.

What is a secondary quality gate for change validation before merge?▼

A secondary quality gate for change validation is a post-lint review step that checks finished feature changes for correctness bugs, naming clarity, and test coverage. It acts as a final review after automated linting passes to catch hidden flaws before merge.

How do I review code changes for edge case oversights and missing test coverage?▼

Review code changes for edge case oversights by running a post-lint quality check after structural linting passes. This process evaluates change sets for missing test coverage, edge cases, and correctness bugs, returning a structured PASS or CHANGES NEEDED verdict sorted by severity.

Can I get an automated code review for correctness bugs after linting passes?▼

Yes, you can get an automated code review for correctness bugs after linting passes by using a sub-agent reviewer. It provides a fresh read of your change set to identify edge case oversights, design flaws, and naming clarity issues not covered by static analysis.

What are the limitations of static analysis tools for software quality?▼

The limitations of static analysis tools for software quality include missing critical correctness bugs, design flaws, and edge case oversights. They focus on structural code smells, so they cannot detect missing test coverage or naming clarity issues without a secondary post-lint review.

Related Skills

Explore More Software Engineering Skills→
OmarMiraOmarMira

lint-and-validate

Run linting and type checks on Node.js/TypeScript and Python projects.

Community
Intermediate
roborewroborew

review

Review pull requests for bugs, security risks, and merge readiness.

Community
Intermediate
KaakatiKaakati
2

test-generator

Generate unit, integration, and E2E tests following the AAA pattern.

Community
Advanced
saschadudkin-sketchsaschadudkin-sketch

code-review

Automate code review for rezidence4/DomHub repository changes.

Community
Advanced