skills.rest
weerachai8266
weerachai8266COMMUNITY
Explore all skills by this author →
GitHub

scrutinize

Trace end-to-end execution paths to assess whether code changes should exist.

Updated Jun 1, 2026
Search Tags:#trace#review#end-to-end#rationale#code-review#scrutinize
One-click install
npx skills add https://github.com/weerachai8266/CWT-maintenance_V2 --skill scrutinize-weerachai8266
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scrutinize
Source: https://github.com/weerachai8266/CWT-maintenance_V2/tree/main/skills/engineering/scrutinize
Command: npx skills add https://github.com/weerachai8266/CWT-maintenance_V2 --skill scrutinize-weerachai8266

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stand outside changes to determine if a plan, PR, or code alteration should exist at all, and to assess whether a simpler or more elegant approach can achieve the same goal.

Core Features & Use Cases

  • Outsider perspective: Ask high-level intent, verify the real end-to-end flow beyond the diff, and identify gaps or inefficiencies.
  • Trace and verify: Follow the actual code path from entry to outcome, gather evidence, and surface actionable recommendations with rationale.
  • Actionable outcomes: Produce concise findings with concrete changes and rationale to inform decisions on plans, PRs, diffs, or designs.

Quick Start

Provide an outsider-end review of a proposed change by tracing the full execution path and delivering actionable recommendations.

Frequently Asked Questions about scrutinize

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

FAQPage Schema
How do I review a pull request from an outsider perspective to see if it should exist?▼

An end-to-end code review traces the actual execution path from entry to outcome, gathering evidence to articulate concise, actionable findings with clear rationale rather than just examining the diff.

Can I sanity-check a design doc to find a simpler approach before implementation?▼

Yes, you can sanity-check a design doc by asking high-level intent questions and verifying the real end-to-end flow to identify gaps, inefficiencies, and simpler approaches before implementation begins.

How do I trace the execution path of a code change to surface actionable findings?▼

Trace the execution path of a code change by following the actual code flow from entry to outcome, collecting evidence to surface actionable recommendations with clear rationale that inform decisions on diffs or designs.

What is the best way to audit a proposed code change and verify its end-to-end flow?▼

The best way to audit a proposed code change is to stand outside the diff, ask high-level intent questions, verify the real end-to-end flow, and deliver concise findings with concrete changes and rationale.

When should I not use an outsider end-to-end review for my plan or PR?▼

You should not use an outsider end-to-end review when you only need a localized syntax check or superficial diff inspection, as this approach focuses on high-level intent, end-to-end execution paths, and simpler alternatives.

Related Skills

Explore More Software Engineering Skills→
danalexilewisdanalexilewis
1

investigate

Synthesize end-of-chat context and docs into a reviewer-only investigation plan.

Community
Intermediate
usoramausorama

code-review

Review code diffs for correctness, security, and maintainability.

Community
Advanced
samjhechtsamjhecht
4

requesting-code-review

Dispatch a code-review subagent to verify implementation against plan or requirements.

Community
Basic
russosalvrussosalv
5

verification-before-completion

Require fresh verification command execution and output inspection before completion claims.

Community
Intermediate