simplify

Included with Lifetime

$97 forever

This skill should be used when the user wants to clean up code without changing behavior. Dispatches cleanup agents, runs tests to verify behavior is preserved, then runs code review. Triggers include "simplify this", "clean up this code", "refactor without changing behavior", "reduce complexity".

Code Review

What this skill does

# Simplify

Orchestrate code cleanup through agent delegation. Preserve behavior. Don't change what the code does.

Act as orchestrator. Dispatch work to sub-agents via the Task tool. Do not edit code directly.

## Input

Invoked as `/simplify` with optional arguments:

- **No args**: simplify files with uncommitted changes (`git status`)
- **File pattern**: simplify files matching the pattern
- **Notes path** (`.lore/work/notes/*.html`): resume a previous session

## Process

**Cleanup.** Dispatch `code-simplifier:code-simplifier` via Task tool with the file list. If `.lore/lore-agents.md` exists, check for additional simplification agents in the Code Quality section and dispatch them too.

**Test.** Dispatch a testing agent via Task tool. Include which files changed and how to run the test suite. Expect pass/fail and notable findings. If tests fail, diagnose and route back to the cleanup agent for correction. After two failed attempts on the same issue, escalate to the user.

**Review.** Dispatch a review agent via Task tool. Include which files to review and the requirement that behavior must be preserved. Route findings back to the cleanup agent for correction. After two failed attempts, escalate to the user.

## Output

Record what happened in a notes file at `.lore/work/notes/simplify-<identifier>.html`. Load `${CLAUDE_PLUGIN_ROOT}/shared/document-schema.md` for the meta tag fields. The body is freeform — capture which files were processed, what was simplified, any failures and how they were resolved.

The output is HTML — a file list with per-file outcome chips (simplified / unchanged / failed), collapsible detail for what changed in each file, and any escalated issues visually flagged. Inline CSS and JS are fine; no external dependencies.

## Escalation

Two conditions require human intervention. Everything else is autonomous.

1. **Stuck loop**: Two consecutive failed attempts on the same test or review failure.
2. **Behavior change detected**: Tests fail in a way that suggests behavior changed rather than a cleanup regression.

Files: 1

Size: 2.4 KB

Complexity: 7/100

Category: Code Review

Source: https://github.com/rjroy/vibe-garden/tree/main/lore-development/skills/simplify

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