quality-severity

Classify issues and code review findings into P1, P2, or P3 severity levels.

1|Updated Jan 12, 2026

Search Tags:#triage #code-review #severity #classify #P3 #P1 #P2

Ready to run

npx skills add https://github.com/jovermier/claude-code-plugins-ip-labs --skill quality-severity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quality-severity
Source: https://github.com/jovermier/claude-code-plugins-ip-labs/tree/main/plugins/dev/skills/quality-severity
Command: npx skills add https://github.com/jovermier/claude-code-plugins-ip-labs --skill quality-severity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines issue triage by consistently mapping findings to severity levels (P1, P2, P3), enabling focused remediation and faster release decisions.

Core Features & Use Cases

Severity mapping: classify issues, findings, or code review problems into P1, P2, or P3.
Triage guidance: provide recommended actions and ownership based on severity.
Use Case: When a security vulnerability is discovered in a PR, classify as P1 and generate immediate remediation tasks.

Quick Start

Use the quality-severity skill to classify a described issue as P1 and receive a prioritized triage plan.

Frequently Asked Questions about quality-severity

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

FAQPage Schema

How do I classify code review findings into priority levels for triage?▼

To classify code review findings for triage, map issues to severity levels like P1, P2, or P3 to guide remediation efforts and prioritize required actions for faster release decisions.

What is the difference between P1, P2, and P3 severity in pull requests?▼

Severity in pull requests distinguishes priority: P1 indicates critical issues like security vulnerabilities requiring immediate remediation, while P2 and P3 represent lower-priority findings mapped to appropriate triage actions.

How do I generate remediation steps for a security vulnerability found in a PR?▼

To generate remediation steps for a security vulnerability in a PR, classify the issue as P1 severity to trigger immediate triage guidance and define required ownership and prioritized actions.

Can I use severity mapping to triage bug reports and feature discussions?▼

Yes, you can use severity mapping to triage bug reports and feature discussions by classifying these findings into P1, P2, or P3 levels to support consistent decision-making and focused remediation.

What is the best way to prioritize issues discovered during code reviews?▼

The best way to prioritize issues discovered during code reviews is to apply severity classification, mapping findings to P1, P2, or P3 levels to determine required actions and streamline release decisions.