code-cleanup

Included with Lifetime

$97 forever

This skill should be used when the user asks to "clean up tests", "clean up code", "tidy up tests", "remove dead tests", "organize test files", "fix test structure", or mentions test hygiene, test bloat, removing temporary tests, or following test best practices. Unlike the code-review skill (which reviews a diff for quality), this skill performs batch cleanup across entire files or directories. Reports issues first, then applies fixes after confirmation.

Code Review

What this skill does

# Code Cleanup

Review and clean up tests and code. Focused on removing bloat, enforcing structure, and following language best practices.

## Workflow

### 1. Determine Scope

Based on the user's request, determine what to review:

- **Uncommitted changes**: Run `git diff --name-only` and `git diff --cached --name-only` to get changed files.
- **Specific files/directories**: Use the paths the user provides.
- **Full scan**: Scan all test files in the repository using language-appropriate patterns:
- Go: `**/*_test.go`
- TypeScript/JavaScript: `**/*.test.{ts,tsx,js}`, `**/*.spec.{ts,tsx,js}`, `**/__tests__/**`
- Python: `**/test_*.py`, `**/*_test.py`

### 2. Analyse

Read each file in scope. Apply the checklist from [checklist.md](references/checklist.md). For each issue found, record:

- **File and line reference** (file:line format)
- **Issue category** (from checklist)
- **What to do** (remove, move, rewrite, etc.)

### 3. Report

Present findings grouped by category. Use this format:

```
## Cleanup Report

### Tests to Remove
- **user_test.go:42** - Trivial test asserting getter returns field value
- **api.test.ts:88** - Empty test body, likely temporary

### Tests to Restructure
- **utils_test.go:15** - Test for `ParseConfig` belongs in `config_test.go`

### Comments to Remove
- **handler.py:23** - Stale TODO referencing resolved issue

### Code to Simplify
- **service.ts:67** - Dead code branch, condition is always false
```

End with a summary count: "Found X issues across Y files."

### 4. Fix

After the user confirms, apply fixes. For each fix:

1. Read the file (always re-read before editing).
2. Apply the change.
3. If moving a test, ensure imports are updated in both source and destination files.
4. Run the test suite after all changes to confirm nothing breaks. If tests fail, investigate and ask or fix it before continuing.

## Principles

- Only flag tests that genuinely add no value. A simple test for tricky logic is fine.
- "Tricky" means: edge cases, error paths, concurrency, parsing, math, state machines.
- Trivial means: testing a getter, testing a constructor sets fields, testing a wrapper that just delegates.
- When restructuring, prefer the convention of the language and project over personal preference.
- Do not add tests. This skill removes and reorganizes, it does not create.

Files: 2

Size: 5.2 KB

Complexity: 21/100

Category: Code Review

Source: https://github.com/denisraison/claude-plugins/tree/main/plugins/workflow-tools/skills/cleanup

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts