code-simplify
The code-simplify slash command refactors recently modified code or a specified scope to improve clarity and maintainability by reducing complexity while preserving behavior. Use this command when code contains deep nesting, overly long functions, unclear variable names, or duplicated logic that should be consolidated into more readable, testable units.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/addyosmani/agent-skills/HEAD/.claude/commands/code-simplify.md -o ~/.claude/commands/code-simplify.mdcode-simplify.md
Invoke the agent-skills:code-simplification skill. Simplify recently changed code (or the specified scope) while preserving exact behavior: 1. Read CLAUDE.md and study project conventions 2. Identify the target code — recent changes unless a broader scope is specified 3. Understand the code's purpose, callers, edge cases, and test coverage before touching it 4. Scan for simplification opportunities: - Deep nesting → guard clauses or extracted helpers - Long functions → split by responsibility - Nested ternaries → if/else or switch - Generic names → descriptive names - Duplicated logic → shared functions - Dead code → remove after confirming 5. Apply each simplification incrementally — run tests after each change 6. Verify all tests pass, the build succeeds, and the diff is clean If tests fail after a simplification, revert that change and reconsider. Use `code-review-and-quality` to review the result.
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.