Does this skill help with debugging?

Yes, it challenges guesswork during debugging by mandating a systematic approach that includes instrumentation, logging, and checking existing traces first.

How does the 'Research First' principle work?

Before asking the user for information, the skill will grep the codebase, check package configurations, and read documentation to find the answer itself.

What core patterns does Critical Peer enforce?

It primarily enforces functional dependency injection (fn(args, deps)), explicit Result types for domain errors, and validation at boundaries using schemas like Zod.

How does Critical Peer handle user disagreements?

It treats questions literally and asks for reasoning. If the user specifies constraints like legacy code or prototyping, the skill acknowledges the exception and adapts.

Why is the output from this skill so concise?

The skill follows a 'signal over noise' philosophy, removing social niceties and filler to provide factual, actionable assessments as quickly as possible.

Critical Peer

Name: Critical Peer
Author: jagreehal

byjagreehal

生産性とワークフロー

Enforces rigorous architectural patterns and professional skepticism to ensure high-quality, consistent code through proactive coaching and pattern enforcement.

概要

Critical Peer acts as a high-standard senior reviewer that prioritizes architectural integrity and logic over pleasantries. It automatically challenges common anti-patterns—such as god objects, unhandled exceptions, and class-based dependency injection—steering the developer toward functional, testable, and explicit patterns like fn(args, deps) and Result-type error handling. This skill is ideal for teams or solo developers who want to maintain strict coding standards, reduce technical debt, and ensure that every line of code is justified by research and pattern adherence.

主な機能

Pattern Enforcement: Automatically identifies and challenges violations of functional dependency injection and Result-type patterns.
Explicit Error Handling: Promotes the use of domain-specific Result types over exceptional error throwing.
Research-First Protocol: Proactively searches documentation and existing codebases to resolve questions without user intervention.
Skeptical Verification: Investigates claims and bug reports thoroughly before agreeing or implementing fixes.
0 GitHub stars
Zero-Fluff Communication: Delivers high-signal, concise feedback by eliminating preambles, praise, and filler text.

ユースケース

Enforcing strict error handling and validation boundaries in high-stakes API development.
Streamlining TDD workflows by ensuring tests cover both success and explicit failure paths.
Refactoring legacy object-oriented code into functional, dependency-injected patterns.

概要

主な機能

Pattern Enforcement: Automatically identifies and challenges violations of functional dependency injection and Result-type patterns.
Explicit Error Handling: Promotes the use of domain-specific Result types over exceptional error throwing.
Research-First Protocol: Proactively searches documentation and existing codebases to resolve questions without user intervention.
Skeptical Verification: Investigates claims and bug reports thoroughly before agreeing or implementing fixes.
0 GitHub stars
Zero-Fluff Communication: Delivers high-signal, concise feedback by eliminating preambles, praise, and filler text.

ユースケース

Enforcing strict error handling and validation boundaries in high-stakes API development.
Streamlining TDD workflows by ensuring tests cover both success and explicit failure paths.
Refactoring legacy object-oriented code into functional, dependency-injected patterns.