skills.rest
alexsandrocruz
alexsandrocruzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

actionable-review-format-standards

Standardize code-review outputs with severity labels and file:line references.

Updated Jan 23, 2026
Search Tags:#templates#feedback#code-review#pull-requests#file-path#severity-labels
One-click install
npx skills add https://github.com/alexsandrocruz/DominusLeads --skill actionable-review-format-standards-alexsandrocruz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: actionable-review-format-standards
Source: https://github.com/alexsandrocruz/DominusLeads/tree/main/backend/Sapienza.Leads/.claude/skills/actionable-review-format-standards
Command: npx skills add https://github.com/alexsandrocruz/DominusLeads --skill actionable-review-format-standards-alexsandrocruz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes code-review outputs to ensure consistent, actionable feedback across teams and PRs, reducing ambiguity and rework.

Core Features & Use Cases

  • Severity-based feedback templates to ensure every issue is labeled with CRITICAL/HIGH/MEDIUM/LOW and includes a file:line reference.
  • Location-aware reporting that enforces file:line location formatting and concise problem statements.
  • Actionable fixes guidance for blocking issues that must be addressed before merge, plus optional suggestions for non-blocking improvements.
  • Use Case: Generate a PR review summary for a multi-file change set, with prioritized issues and recommendations.

Quick Start

Provide a PR patch or code snippet as input and request a structured review report that highlights critical defects and suggested fixes.

Frequently Asked Questions about actionable-review-format-standards

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

FAQPage Schema
How do I standardize code review feedback for pull requests?▼

Standardizing code review feedback involves enforcing a fixed structure with severity labels like CRITICAL or LOW, alongside precise file:line references. This ensures uniform, actionable feedback across all pull requests and reduces ambiguity for developers.

What is the best way to format code review comments for automation pipelines?▼

Formatting code review comments for automation pipelines requires a consistent structure with severity mapping and location syntax. This uniform format allows automated systems to parse blocking issues and optional fix snippets reliably.

How do I generate a structured PR review report with prioritized issues?▼

To generate a structured PR review report, provide a PR patch or code snippet as input to receive a standardized output. The report highlights critical defects first, using severity labels and file:line references to prioritize issues and recommendations.

Does this code review template require specific severity labels for blocking issues?▼

Yes, the code review template requires specific severity labels such as CRITICAL, HIGH, MEDIUM, or LOW for every issue. Blocking issues must be labeled and addressed before merge, often including optional fix snippets to guide the developer.

Can I use this format for code audits on multi-file change sets?▼

Yes, you can use this format for code audits on multi-file change sets. It enforces location-aware reporting with file:line location formatting, ensuring concise problem statements and actionable fixes guidance across all modified files.

Related Skills

Explore More Software Engineering Skills→
JustinFirschingJustinFirsching

code-review

Review code changes for quality, correctness, and maintainability using a structured checklist.

Community
Intermediate
khoabdkhoabd

code-review-quality

Reviews code for correctness, security, |performance, and maintainability defects with severity classifications.

Community
Intermediate
thapaliyabikendrathapaliyabikendra
24

actionable-review-format-standards

Standardize code review outputs with severity labels, file:line references, and fix snippets.

Community
Advanced
jacobjmcjacobjmc
1

priority-review

Review code diffs and PRs for P0-P3 severity defects.

Community
Advanced