review

Filters flagged code issues by confidence threshold for reporting.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/paxtone-studio/openkodo --skill review-paxtone-studio
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/paxtone-studio/openkodo/tree/main/plugins/kodo/skills/review
Command: npx skills add https://github.com/paxtone-studio/openkodo --skill review-paxtone-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the code review process by focusing only on high-confidence issues, reducing noise and ensuring critical problems are addressed without getting bogged down in minor details.

Core Features & Use Cases

  • Confidence-Based Filtering: Only reports issues with 80% or higher confidence, filtering out stylistic preferences and uncertain concerns.
  • Structured Reporting: Provides a clear, actionable format for reporting bugs, security issues, and quality problems.
  • Use Case: When merging a new feature, use this Skill to perform a thorough review, ensuring that only critical bugs and security vulnerabilities are flagged, allowing for faster, more confident merges.

Quick Start

Use the review skill to analyze the code changes in the current branch for critical issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a high-confidence code review to catch critical bugs?β–Ό

A high-confidence code review identifies critical bugs, security vulnerabilities, and quality issues using a strict confidence-based filtering mechanism that only reports problems with an 80% or higher certainty to ensure actionable feedback.

Why should I filter code review issues by an 80% confidence threshold?β–Ό

Filtering code review issues by an 80% confidence threshold reduces noise from stylistic preferences and uncertain concerns, ensuring developers only address critical bugs and significant quality problems for faster merges.

How do I identify security vulnerabilities and critical bugs in Rust code?β–Ό

To identify security vulnerabilities and critical bugs, the review process utilizes project-specific context and established patterns, applying a minimum 80% confidence threshold to filter out uncertain concerns and provide structured feedback.

What is the best way to streamline code reviews for faster feature merges?β–Ό

The best way to streamline code reviews for faster merges is to use confidence-based filtering that focuses exclusively on critical bugs and security vulnerabilities, avoiding minor details and stylistic preferences.

Does this code review process integrate with knowledge capture systems?β–Ό

Yes, the code review process integrates with Kodo for knowledge capture, guiding users through context gathering, issue identification, documentation, and feedback handling to maintain comprehensive project records.

Can I use confidence filtering for quality assurance on any code changes?β–Ό

Yes, you can apply confidence filtering to any code changes by analyzing the branch for critical issues, prioritizing significant quality problems and security vulnerabilities that meet the strict 80% reporting threshold.