code-review-yagni-detector

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

Flag YAGNI violations in code diffs during code reviews.

21|8|Updated Mar 9, 2026

Search Tags:#refactoring #maintainability #yagni #code-review #dead-code #premature-optimization #speculative-features

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YAGNI violations add maintenance burden by encouraging speculative features, unused code paths, and premature optimizations. This skill helps teams identify and prune these inefficiencies before they become costly to maintain.

Core Features & Use Cases

Automated PR and code-diff reviews to surface speculative features, dead code, and over-configuration.
Enforces a structured review workflow with traceability and actionable remediation guidance.
Generates a prioritized list of refactor actions to minimize maintenance overhead and improve code clarity.

Quick Start

Review the latest commit to identify speculative features, unused code paths, and premature optimizations that add maintenance burden.

Frequently Asked Questions about code-review-yagni-detector

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

FAQPage Schema

How do I detect speculative features and dead code in a pull request?▼

To detect speculative features and dead code in a pull request, analyze code diffs against current requirements to identify unused code paths and over-configuration. This process flags unnecessary abstractions before they merge, providing actionable remediation guidance to prune inefficiencies.

What is a YAGNI violation and how do I identify it during code reviews?▼

A YAGNI violation is the inclusion of speculative features, premature optimizations, or unused options not required by current needs. Identify these violations during code reviews by analyzing new changes against existing requirements to flag dead code and over-configuration with traceability.

How do I find premature optimizations and unnecessary abstractions in my codebase?▼

Find premature optimizations and unnecessary abstractions by reviewing code diffs to enforce a structured workflow with traceability. This analysis prioritizes removal or deferment of unused options and speculative code paths, minimizing maintenance overhead and improving overall code clarity.

What's the best way to automate dead code detection for refactoring?▼

Automate dead code detection for refactoring by applying automated PR reviews that surface speculative features and over-configuration. This generates a prioritized list of refactor actions targeting unnecessary abstractions, ensuring maintenance burden is minimized before changes surface.

Can I use code review automation to flag unused options across design artifacts?▼

Yes, you can use code review automation to flag unused options across PRs and design artifacts. It analyzes new changes against current requirements to detect over-configuration and speculative features, enforcing a review workflow with traceability for actionable removal.

When should I defer or remove unnecessary abstractions in my code?▼

Defer or remove unnecessary abstractions when code review analysis identifies them as speculative features, dead code, or premature optimizations not tied to current requirements. Prioritize removal to minimize maintenance burden and improve code clarity across the codebase.