cleanup

Review code changes for clean code principles and anti-patterns.

2|Updated Jul 11, 2024
One-click install
npx skills add https://github.com/nicograef/handbook --skill cleanup-nicograef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleanup
Source: https://github.com/nicograef/handbook/tree/main/.claude/skills/cleanup
Command: npx skills add https://github.com/nicograef/handbook --skill cleanup-nicograef

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the accumulation of technical debt and AI-generated code smells by providing a structured, incremental review process that enforces clean code principles without requiring manual oversight for every minor detail.

Core Features & Use Cases

  • Multi-Pass Quality Review: Systematically checks code for readability, structural smells, architectural boundary violations, and AI-generated slop.
  • Context-Aware Analysis: Reviews changes based on existing project conventions rather than imposing foreign styles.
  • Use Case: Use this skill after a feature implementation to ensure the new code adheres to SOLID principles, removes unnecessary abstractions, and maintains consistent architectural boundaries before merging.

Quick Start

Run the cleanup skill on the current staged changes to identify and report code quality improvements.

Frequently Asked Questions about cleanup

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

FAQPage Schema
How do I review code changes for clean code principles and anti-patterns?

Code changes are reviewed through a multi-pass process that checks for readability, structural smells, and architectural boundary violations to ensure maintainability. This enforces clean code principles by providing concrete, minimal refactoring suggestions based on existing project conventions.

What is the best way to detect AI-generated code smells and unnecessary abstractions?

Detecting AI-generated code smells is handled by integrated AI-slop detection that identifies unnecessary abstractions and enforces consistency. It systematically reviews code to remove generated artifacts and ensure adherence to SOLID principles.

Can I run static analysis on staged, unstaged, or committed code scopes?

Static analysis can be operated on staged, unstaged, or committed code scopes to provide targeted context-aware reviews. This allows you to incrementally review specific changes and enforce architectural boundaries before merging.

How does context-aware analysis handle existing project conventions during refactoring?

Context-aware analysis reviews changes based on existing project conventions rather than imposing foreign styles. It ensures that refactoring suggestions for technical debt reduction are minimal, concrete, and consistent with the current codebase architecture.

When do I need an automated code review to manage technical debt?

An automated code review is needed when technical debt and AI-generated code smells accumulate without manual oversight. It provides a structured, incremental review process to enforce architectural boundaries and clean code principles after feature implementation.