skills.rest
luiztrilha
luiztrilhaCOMMUNITY
Explore all skills by this author →
GitHub

code-review-findings

Identify and rank bugs, regressions, risks, and missing tests in code changes.

Updated Apr 27, 2026
Search Tags:#code review#code analysis#development workflow#risk assessment#bug finding
One-click install
npx skills add https://github.com/luiztrilha/dunderia-public --skill code-review-findings
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-findings
Source: https://github.com/luiztrilha/dunderia-public/tree/main/templates/local-runtime-profile/skills/codex/code-review-findings
Command: npx skills add https://github.com/luiztrilha/dunderia-public --skill code-review-findings

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, focusing on identifying bugs, regressions, risks, and missing tests in code changes.

Core Features & Use Cases

  • Findings-First Approach: Prioritize and present technical findings over summaries.
  • Review Priorities: Correctness bugs, regressions, validation, security risks, performance, and maintainability issues.
  • Use Case: Ideal for a developer or team lead who needs a comprehensive review of code changes, focusing on critical issues.

Quick Start

Run the skill to review the changes in your codebase for potential issues.

Frequently Asked Questions about code-review-findings

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

FAQPage Schema
How do I prioritize code review findings for bugs and regressions?▼

Code review findings for bugs and regressions are prioritized by analyzing code changes to identify and rank technical issues, focusing on correctness bugs, regressions, validation, security risks, performance, and maintainability problems.

What is a findings-first approach to code analysis?▼

A findings-first approach to code analysis prioritizes and presents technical findings over summaries. It identifies bugs, regressions, risks, and missing tests in code changes to provide actionable insights during code reviews and patch assessments.

How do I assess risks and missing tests in a pull request?▼

To assess risks and missing tests in a pull request, interpret and analyze the code changes to identify potential regressions, security risks, performance issues, and maintainability problems, ranking them to provide actionable insights for the review workflow.

Can I use automated code analysis for patch assessments and PR audits?▼

Yes, you can use automated code analysis for patch assessments and PR audits. This process interprets code changes to identify and rank technical findings, focusing on bugs, regressions, validation, security risks, and missing tests within code review workflows.

Does code review analysis work for identifying security risks and performance issues?▼

Yes, code review analysis works for identifying security risks and performance issues. It evaluates code changes to rank technical findings, covering correctness bugs, validation, security risks, performance, and maintainability issues to deliver actionable insights.

Related Skills

Explore More Software Engineering Skills→
mejangomejango

sarif-parsing

Parse SARIF 2.1.0 files to extract and deduplicate findings.

Community
Intermediate
mvillmowmvillmow
18

gh-implement-issue

Automate GitHub issue implementation from branch creation to pull request.

Community
Intermediate
dhruvinrsonidhruvinrsoni

testing-strategy

Analyze test pyramid structure and coverage gaps to define testing strategies.

Community
Advanced
jdiegosierrajdiegosierra
1

security-review

Audit web applications and infrastructure for security vulnerabilities and compliance.

Community
Advanced