honest-review

Analyze code correctness, design, and efficiency with confidence-scored findings.

4|1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/wyattowalsh/agents --skill honest-review
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: honest-review
Source: https://github.com/wyattowalsh/agents/tree/main/skills/honest-review
Command: npx skills add https://github.com/wyattowalsh/agents --skill honest-review

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates code review, identifying defects, design flaws, and inefficiencies with confidence scores and research-backed evidence, ensuring higher code quality and faster development cycles.

Core Features & Use Cases

  • Comprehensive Code Analysis: Reviews code at Correctness, Design, and Efficiency levels.
  • Evidence-Based Findings: Every non-trivial finding is validated with external research (Context7, WebSearch, gh).
  • Confidence Scoring: Findings are scored 0.0-1.0, with clear reporting for confirmed vs. unconfirmed issues.
  • Creative Lenses: Applies lenses like Adversary, Inversion, and Newcomer to uncover hidden issues.
  • Automated Fixes: Offers to generate and apply fixes based on review findings, with previews and verification.
  • Use Case: Integrate into your CI/CD pipeline to automatically flag potential security vulnerabilities, performance bottlenecks, or design anti-patterns before they reach production.

Quick Start

Use the honest-review skill to audit the entire codebase for potential issues.

Frequently Asked Questions about honest-review

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

FAQPage Schema
How do I automate code review in my CI/CD pipeline?โ–ผ

Automating code review in CI/CD pipelines involves analyzing correctness, design, and efficiency using static analysis, then outputting findings as SARIF reports and conventional comments to flag security vulnerabilities and bottlenecks before production.

How does evidence-based static analysis validate code findings?โ–ผ

Evidence-based static analysis validates code findings by cross-referencing non-trivial issues against external research using tools like WebSearch and Context7, assigning a 0.0-1.0 confidence score to distinguish confirmed defects from unconfirmed potential flaws.

Can I perform a full codebase audit for design anti-patterns?โ–ผ

Yes, you can perform a full codebase audit to identify design anti-patterns by applying multiple creative lenses like Adversary and Inversion, ensuring comprehensive detection of structural flaws and inefficiencies across the entire repository.

What is the best way to generate automated refactoring fixes from a security audit?โ–ผ

Generating automated refactoring fixes from a security audit involves analyzing the codebase for vulnerabilities, offering to generate fixes based on confidence-scored findings, and applying them with previews and verification steps.

Does SARIF output work with conventional comments for pull request analysis?โ–ผ

SARIF output integrates seamlessly with conventional comments for pull request analysis, translating confidence-scored static analysis findings into structured, readable feedback directly within the code review workflow.

What are the limitations of confidence-scored code review findings?โ–ผ

Confidence-scored code review findings range from 0.0 to 1.0, meaning lower scores indicate unconfirmed issues requiring manual verification, while higher scores represent validated defects backed by external research evidence.