skills.rest
jakkaret
jakkaretCOMMUNITY
Explore all skills by this author →
GitHub

scrutinize

Review code changes for correctness, efficiency, and best practices.

2|Updated Jan 13, 2026
Search Tags:#quality assurance#code review#code analysis#change review#rationale-driven
One-click install
npx skills add https://github.com/jakkaret/waf_project --skill scrutinize-jakkaret
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scrutinize
Source: https://github.com/jakkaret/waf_project/tree/main/.agents/skills/scrutinize
Command: npx skills add https://github.com/jakkaret/waf_project --skill scrutinize-jakkaret

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of thorough code review, ensuring that changes are vetted not just for correctness, but also for efficiency and elegance.

Core Features & Use Cases

  • Outsider Perspective: Reviews code from an unbiased perspective, considering alternatives and suggesting improvements.
  • End-to-End Code Path Analysis: Follows the actual code execution path, not just the diff, to ensure the change behaves as intended.
  • Concise and Actionable Feedback: Provides clear, actionable feedback with rationale, focusing on what to change, why, and with supporting evidence.

Quick Start

Use the /scrutinize command to get a detailed review of your code change or PR.

Frequently Asked Questions about scrutinize

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

FAQPage Schema
How do I get a thorough code review for a pull request?▼

To get a thorough code review for a pull request, use rationale-driven scrutiny to analyze the full code path for correctness, efficiency, and best practices. It provides actionable feedback with supporting evidence on your changes.

What is the best way to analyze code changes for efficiency and correctness?▼

The best way to analyze code changes for efficiency and correctness is by evaluating the entire execution path rather than just the diff. This approach ensures the change behaves as intended and adheres to best practices.

Can I review just a diff or do I need the full code path?▼

You can provide a diff, but a comprehensive code review requires analyzing the full code path. Following the actual execution path ensures the change behaves accurately as intended within the broader codebase.

How does a rationale-driven code review improve code quality?▼

A rationale-driven code review improves code quality by providing clear, actionable feedback that explains what to change and why. It evaluates changes from an unbiased perspective, suggesting improvements with supporting evidence.

Does automated code analysis work on different types of codebases?▼

Yes, rationale-driven code analysis operates on a variety of codebases and change types. It reviews changes for correctness and efficiency regardless of the specific codebase or change format.

Related Skills

Explore More Software Engineering Skills→
zyj18860969891-bytezyj18860969891-byte

diffs

Generate shareable diffs and patch views with viewer URLs and file artifacts.

Community
Intermediate
peancharoenpeancharoen

speckit.reviewer

Review git diffs and file paths for code issues with severity labels.

Community
Intermediate
aaddrickaaddrick
5.3k

lint

Lint shell scripts with shellcheck and GitHub Actions workflows with actionlint.

Community
Basic
SivanwolSivanwol

laravel-iterating-on-code

Generate structured feedback to improve AI-generated PHP code.

Community
Advanced