Detect duplication, complexity, and over-engineering in batch code changes.
npx skills add https://github.com/jstoup111/ai-conductor --skill simplify-jstoup111
Please help me install this Agent Skill. Skill: simplify Source: https://github.com/jstoup111/ai-conductor/tree/main/skills/simplify Command: npx skills add https://github.com/jstoup111/ai-conductor --skill simplify-jstoup111
The simplify Skill identifies duplication, complexity, and over-engineering in code at the boundary of a batch, acting as a gate before the next batch proceeds, ensuring a clean codebase.
Duplication Detection: Identifies and flags duplicated business logic across batch-changed files.
Complexity Assessment: Flags methods with high conditional branches, method length, nesting depth, and parameter count.
Over-Engineering Flagging: Flags unnecessary abstractions, such as single-caller abstractions, unnecessary wrappers, or premature generalization.
Dead Code Detection: Identifies code that has been added but never called.
Batch Boundary Checks: Operates only at the boundaries of batches, analyzing only the files that have been changed within that batch.
Use Case: Consider a batch of code changes; simplify will check this batch for potential quality issues, such as code duplication and unnecessary complexity, which helps maintain a clean and maintainable codebase.
Run the simplify Skill after making changes in the current batch to review for quality issues before proceeding.
High-intent search queries and answers about installing and using this skill.
To detect code duplication and complexity in batch changes, run a batch boundary check to flag duplicated business logic, high conditional branches, and deep nesting in modified files. This ensures a clean codebase before proceeding.
Over-engineering detection in code review flags unnecessary abstractions, single-caller abstractions, unnecessary wrappers, and premature generalization to prevent over-complication within a batch of code changes.
Check for dead code and unnecessary abstractions by analyzing changed files at batch boundaries to identify never-called code, single-caller wrappers, and premature generalizations before proceeding.
Complexity management for batch boundaries requires no external dependencies to run locally, analyzing only the files changed within that specific batch for quality control and optimization.
Use batch boundary checks for code quality after making changes in the current batch to review for duplication, complexity, and over-engineering issues before proceeding to the next batch.
adryanmoldokkr32-pixelBlock Edit and Write operations outside a configured directory boundary.
drvossRefactor complex or duplicated code with test-driven incremental steps.
nguyenphpRun linters, type checkers, and security audits across Node.js and Python projects.
T-ravAudit test files for naming, structure, coverage, and fixture gaps.
