skills.rest
thrillmade
thrillmadeOFFICIAL
Explore all skills by this author →
GitHub

critical-issues-only

Flag bugs, security vulnerabilities, and performance issues in pull requests.

1|Updated May 15, 2026
Search Tags:#code quality#PR review#critical analysis#performance auditing#issue flagging
One-click install
npx skills add https://github.com/thrillmade/agent-skills --skill critical-issues-only
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: critical-issues-only
Source: https://github.com/thrillmade/agent-skills/tree/main/.claude/skills/critical-issues-only
Command: npx skills add https://github.com/thrillmade/agent-skills --skill critical-issues-only

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that pull request reviews focus on critical correctness, security, and performance issues, enhancing review efficiency and quality.

Core Features & Use Cases

  • Selective Issue Identification: Identifies and flags only bugs, vulnerabilities, and performance problems.
  • Skipping Non-Critical Issues: Excludes style preferences, architectural changes, and minor nits.
  • Phrasing Findings: Encourages clear, actionable feedback for each identified issue.
  • Use Case: By using this Skill, a team can maintain a high-quality codebase with a streamlined review process, focusing on the most impactful issues.

Quick Start

Use the critical-issues-only skill during a PR review session to filter out and flag only critical issues in the code.

Frequently Asked Questions about critical-issues-only

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

FAQPage Schema
How do I flag only critical PR issues during a code review?▼

Critical issue flagging in pull requests targets only bugs, security vulnerabilities, and performance problems. It skips non-critical style preferences, architectural changes, and minor nits to maintain review efficiency and focus on impactful codebase quality.

Can I use critical issue flagging for PRs without a formal review process?▼

Critical issue flagging requires a codebase with a pull request system and an established review process in place. It is designed to filter and streamline existing review sessions rather than function as a standalone quality gate.

What is the best way to streamline pull request reviews for a large codebase?▼

The best way to streamline pull request reviews is to selectively identify and flag only critical issues like bugs and performance vulnerabilities. Skipping non-critical architectural changes and style nits reduces review overhead while maintaining codebase quality.

What types of non-critical issues are skipped during a performance auditing PR review?▼

A performance auditing PR review skips non-critical issues including style preferences, architectural changes, and minor nits. It focuses exclusively on identifying and phrasing actionable feedback for bugs, security vulnerabilities, and performance problems.

How do I phrase code review findings for security vulnerabilities and bugs?▼

To phrase code review findings for security vulnerabilities and bugs, provide clear, actionable feedback for each identified issue. This ensures developers can immediately understand and resolve the critical correctness and performance problems flagged in the pull request.

Related Skills

Explore More Software Engineering Skills→
CAPHTECHCAPHTECH
1

critical-code-review

Review code changes and generate structured issue lists with fix suggestions.

Official
Advanced
diriendirien
19

review

Review code changes for security, correctness, and quality issues.

Community
Intermediate
winsorllcwinsorllc

code-review

Execute linters, static analysis, and security scanners on code.

Community
Intermediate
ChoiHyunjinChoiHyunjin

role-code-reviewer

Review code against specifications and architectural conventions with severity levels.

Community
Advanced