findings-classifier

Name: findings-classifier
Availability: InStock
Author: shakhovskiya-create

Consolidate audit findings into a severity-ranked remediation backlog.

Updated May 5, 2026

Search Tags:#automation #audit #prioritization #backlog #deduplication #severity #findings

Ready to run

npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill findings-classifier

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: findings-classifier
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/sdlc-audit/skills/findings-classifier
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill findings-classifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-processing of raw findings from all audit phases to deduplicate, assign severity, and produce a final priority-ordered backlog.

Core Features & Use Cases

Consolidate findings from multiple audit phases into a single, unified list.
Deduplicate overlapping findings across phases while preserving evidence and phase origin.
Assign accurate severity and generate a prioritized backlog with actionable remediation items.

Quick Start

Run the classifier after all audit phases complete to generate a prioritized backlog of findings from the collected data.

Frequently Asked Questions about findings-classifier

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

FAQPage Schema

How do I consolidate audit findings from multiple phases into a single backlog?▼

Consolidating audit findings requires merging outputs from architecture, code, and security phases into a unified list. This process deduplicates overlapping findings while preserving evidence and phase origin, resulting in a single priority-ordered backlog ready for remediation.

How do I deduplicate overlapping findings across different audit phases?▼

Deduplicating overlapping findings involves processing collected audit data to identify repeated issues across architecture, code, and security phases. The system preserves evidence and phase origin while removing redundancies, producing a clean backlog for remediation.

Can I customize severity assignments and effort estimates for audit findings?▼

Severity assignments and effort estimates can be customized using an optional audit.config.yaml file. This allows fine-tuning of deduplication rules, severity rankings, and effort estimates to match specific post-audit workflow requirements.

What file formats do I need to run a findings classifier for post-audit workflows?▼

Running a findings classifier requires access to findings.json outputs generated from all completed audit phases. An optional audit.config.yaml file can also be provided to apply custom overrides for deduplication and severity ranking.

When should I generate a prioritized backlog from raw audit findings?▼

A prioritized backlog should be generated after all audit phases complete. Running the classification process at this stage ensures all raw findings from architecture, code, and security audits are collected and available for deduplication and severity ranking.

What is the best way to turn raw security and code audit findings into actionable remediation items?▼

The best way to turn raw audit findings into actionable remediation items is to apply automated deduplication and severity ranking. This consolidates data across phases into a unified, priority-ordered backlog that clearly identifies the most critical issues.