skills.rest
Aimeerrhythm
AimeerrhythmCOMMUNITY
Explore all skills by this author →
GitHub

risk-classifier

Classify risk levels of code changes and route downstream workflow skills.

1|Updated Apr 12, 2026
Search Tags:#automation#workflow#classification#risk#phase2#phase1#ecw
One-click install
npx skills add https://github.com/Aimeerrhythm/enterprise-change-workflow --skill risk-classifier
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: risk-classifier
Source: https://github.com/Aimeerrhythm/enterprise-change-workflow/tree/main/skills/risk-classifier
Command: npx skills add https://github.com/Aimeerrhythm/enterprise-change-workflow --skill risk-classifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly determine the risk level of any code change or requirement to decide how deeply to validate, test, and verify across the ECW workflow, preventing missed impacts or unnecessary work.

Core Features & Use Cases

  • Phase-based risk classification (Phase 1 quick pre-assessment, Phase 2 precise classification, Phase 3 calibration) to tailor downstream routing.
  • Entry point for all change-type tasks and automatic routing to downstream skills based on risk level.
  • Supports cross-domain analysis and dependency knowledge to inform plan writing and implementation.

Quick Start

Describe your requested change, and I will classify its risk level and initiate the appropriate downstream workflow.

Frequently Asked Questions about risk-classifier

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

FAQPage Schema
How do I classify the risk level of a code change to determine testing depth?▼

To classify code change risk, describe your requested change to trigger a phase-based assessment that identifies affected domains, change types, and business sensitivity, ultimately routing the task to the correct downstream workflow depth.

What is phase-based risk classification for software change requests?▼

Phase-based risk classification is a multi-stage process using Phase 1 quick pre-assessment, Phase 2 precise classification, and Phase 3 calibration to evaluate change types and business sensitivity, driving the depth of downstream validation and verification workflows.

How do I route a bug report to the correct downstream workflow based on business impact?▼

Routing bug reports requires classifying their risk implications first; once the risk level is determined through the phased assessment, the task is automatically directed to downstream skills like requirements-elicitation, writing-plans, impl-verify, or biz-impact-analysis.

Can I use risk classification to prevent unnecessary validation for low-risk features?▼

Yes, risk classification is designed to tailor workflow depth; by distinguishing high-risk changes from low-risk ones, it prevents missed impacts on critical domains while avoiding unnecessary validation work for simpler, low-sensitivity feature requests.

When do I need to perform a cross-domain dependency analysis for a code change?▼

You need cross-domain dependency analysis when a code change risk classification indicates high business sensitivity or broad domain impact, ensuring that downstream plan writing and implementation verification account for all affected system interactions.

Related Skills

Explore More Software Engineering Skills→
jellyrockjellyrock
37

issue-triage

Fetch GitHub issues via gh, classify them, and identify code areas.

Official
Advanced
AimeerrhythmAimeerrhythm
1

biz-impact-analysis

Generate a structured business impact report from git diffs and ECW mappings.

Community
Advanced
AimeerrhythmAimeerrhythm
1

writing-plans

Create risk-aware implementation plans from specs with ECW domain context.

Community
Advanced
AZANIRAZANIR
2

qa-risk-analyzer

Rank testing effort by complexity, change frequency, and test coverage.

Community
Advanced