severity

Classify software review findings into five standardized severity levels.

1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/lklimek/claudius --skill severity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: severity
Source: https://github.com/lklimek/claudius/tree/main/skills/severity
Command: npx skills add https://github.com/lklimek/claudius --skill severity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized framework for classifying the severity of findings in code reviews, audits, and assessments, ensuring consistent and objective risk evaluation.

Core Features & Use Cases

  • Standardized Severity Levels: Defines clear levels (CRITICAL, HIGH, MEDIUM, LOW, INFO) with descriptions and CVSS equivalents.
  • Numeric Mapping: Provides an integer mapping for programmatic use.
  • Use Case: When an automated security scan identifies a potential vulnerability, this Skill's guidelines help developers consistently assign a severity level (e.g., HIGH) to prioritize the fix.

Quick Start

Use the severity skill to understand how to classify a code quality finding.

Frequently Asked Questions about severity

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

FAQPage Schema
How do I consistently classify severity levels for code review findings?

To classify severity consistently in code review findings, use a standardized framework mapping five qualitative levels (CRITICAL to INFO) to numerical values based on impact and likelihood. This ensures objective risk evaluation across audits.

What is the standard way to map severity ratings to numerical values in risk assessment?

Severity ratings in risk assessment map five distinct levels—CRITICAL, HIGH, MEDIUM, LOW, and INFO—to integer values for programmatic use. This numeric mapping provides clear rules for consistent application and CVSS equivalents.

How do I assign a severity level when an automated security scan identifies a vulnerability?

When an automated security scan identifies a vulnerability, assign a severity level by applying standardized guidelines based on the finding's impact and likelihood, matching it to one of five defined levels from CRITICAL to INFO.

Does this severity classification framework support quantitative and qualitative risk evaluation?

Yes, this severity classification framework supports both qualitative and quantitative risk evaluation by defining five distinct severity levels with descriptions and mapping them to equivalent CVSS scores and integer values for programmatic use.

When do I need a standardized severity rating system for software development audits?

You need a standardized severity rating system for software development audits when you require consistent, objective risk evaluation across multiple findings. It ensures clear prioritization of code quality and security vulnerabilities during reviews.

Why should I use a defined severity scale instead of ad-hoc ratings for code quality findings?

Using a defined severity scale instead of ad-hoc ratings for code quality findings ensures consistent risk evaluation. It provides clear examples and rules across five levels, preventing subjective bias during security audits and reviews.