simplify

Remove dead code and duplication from a branch diff after tests pass.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill simplify-friedbotstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/simplify
Command: npx skills add https://github.com/friedbotstudio/baseline --skill simplify-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes mechanical clutter from a branch diff after the work is already functionally complete, helping a codebase stay smaller, clearer, and easier to review.

Core Features & Use Cases

  • Mechanical cleanup: Deletes dead code, duplicated logic, over-abstraction, commented-out code, and placeholder stubs.
  • Structure-aware review: Applies a code-structure pass to catch mixed abstraction levels, orchestration leakage, and oversized files.
  • Safe verification loop: Re-runs the configured test command, records the verdict, and either continues with the branch or reverts changes when tests fail.
  • Use case: After a feature branch passes tests, use this Skill to simplify the diff without changing public APIs or adding new behavior.

Quick Start

Use the simplify skill to clean the current branch diff, re-run the project tests, and report whether the cleanup passed or had to be reverted.

Frequently Asked Questions about simplify

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

FAQPage Schema
How do I clean up dead code and reduce duplication in a branch diff before review?

Branch diff cleanup removes mechanical clutter like dead code, duplicated logic, and commented-out stubs. This Skill applies structure-aware review to shrink the diff after tests pass, keeping the codebase smaller and easier to review without altering public APIs.

When should I run code refactoring and cleanup on my feature branch?

Code refactoring and cleanup should run after your feature branch is functionally complete and tests pass. This Skill targets the post-test simplify phase, removing over-abstraction and placeholder stubs without introducing new behavior.

What is the safest way to verify code cleanup does not break existing tests?

Safe test verification requires re-running the configured test command after cleanup. This Skill records the test verdict inline, continuing with the branch if tests pass or automatically reverting changes when tests fail.

Can I simplify a codebase diff without changing public APIs?

Yes, simplifying a codebase diff without changing public APIs is possible using strict guardrails. This Skill preserves public APIs during mechanical cleanup, catching mixed abstraction levels and orchestration leakage while ensuring no new behavior is added.

What happens if test verification fails during automated code maintenance?

If test verification fails during automated code maintenance, the cleanup changes are reverted. This Skill enforces a safe verification loop that updates state files and reverts modifications to ensure the branch remains stable when tests fail.

Does mechanical cleanup catch oversized files and orchestration leakage?

Yes, mechanical cleanup catches oversized files and orchestration leakage through a structure-aware review pass. This Skill identifies mixed abstraction levels and structural issues in the branch diff after functional completion.