code-review-ssot-detector

Name: code-review-ssot-detector
Availability: InStock
Author: Speednet

Detect SSOT violations across configurations, schemas, and code.

21|8|Updated Mar 9, 2026

Search Tags:#risk-assessment #static-analysis #code-review #ssot #config-duplication #type-duplication #constants-duplication

Ready to run

npx skills add https://github.com/speednet-software/speedwave --skill code-review-ssot-detector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-ssot-detector
Source: https://github.com/speednet-software/speedwave/tree/main/.claude/skills/code-review-ssot-detector
Command: npx skills add https://github.com/speednet-software/speedwave --skill code-review-ssot-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Single Source of Truth violations threaten maintainability by scattering authoritative data and definitions across configurations, schemas, and code.

Core Features & Use Cases

Identifies duplicated configurations, duplicate type/schema definitions, and scattered constants
Analyzes semantic equivalences and drift risk to determine canonical sources
Produces actionable remediation plans and suggested canonical location for SSOT

Quick Start

Run a targeted SSOT scan across configurations, types, and constants to surface drift and propose canonical sources.

Frequently Asked Questions about code-review-ssot-detector

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

FAQPage Schema

How do I detect single source of truth violations across configuration files and code?▼

You can detect SSOT violations by scanning configuration values, type definitions, and constants to uncover duplication, drift, and semantic mismatches. The scan identifies scattered authoritative data and produces canonical-source recommendations to restore integrity.

What is configuration drift and how does it affect maintainability?▼

Configuration drift occurs when duplicated values across configs and code become inconsistent over time, threatening maintainability. Analyzing semantic equivalences and drift risk helps determine the canonical source and prioritize remediation steps to fix the inconsistencies.

How do I find duplicate type definitions and scattered constants in my codebase?▼

Finding duplicate type definitions and scattered constants requires a targeted scan across schemas and code. The analysis surfaces duplicated definitions and provides actionable remediation plans suggesting a canonical location to consolidate them.

Can I assess the risk of duplicated constants without a specific static analysis dependency?▼

Yes, you can assess the risk of duplicated constants without external dependencies. The scan evaluates drift risk and semantic mismatches directly within your configurations and code to recommend a canonical source.

What is the best way to remediate duplicated schema definitions and restore SSOT integrity?▼

The best way to remediate duplicated schema definitions is to follow actionable remediation plans generated after a targeted scan. These plans suggest a canonical location for your types and configurations to restore SSOT integrity.

When should I scan for semantic mismatches in my configuration values?▼

You should scan for semantic mismatches when configurations are scattered across multiple files and code. Running a targeted scan identifies drift risk early and provides canonical-source recommendations before inconsistencies impact maintainability.