simplify

Inline abstractions and remove speculative code while verifying tests pass.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/AvatarGanymede/pcraft --skill simplify-avatarganymede
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify
Source: https://github.com/AvatarGanymede/pcraft/tree/main/.agents/skills/simplify
Command: npx skills add https://github.com/AvatarGanymede/pcraft --skill simplify-avatarganymede

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of post-implementation code cleanup, helping developers simplify their codebase while preserving all original functionality.

Core Features & Use Cases

  • Code Simplification: Identifies and inlines one-off abstractions, removes speculative code, reduces nesting, and replaces cleverness with clarity.
  • Post-Implementation: Designed to be run after feature implementation to ensure the codebase remains maintainable.
  • Verification: Includes a verify sub-agent to ensure tests, lints, and typechecks still pass after simplifications.

Quick Start

Run the simplify skill on your recent changes to streamline your codebase.

Frequently Asked Questions about simplify

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

FAQPage Schema
How do I clean up and simplify code after feature implementation?

Post-implementation code cleanup is achieved by inlining one-off abstractions, removing speculative elements, and reducing nesting. This process streamlines the codebase while verifying that all original functionality remains intact.

What is the best way to remove speculative code without breaking existing tests?

Removing speculative code safely requires a verification step that runs tests, lints, and typechecks. This ensures any simplifications or removed abstractions do not break existing functionality or introduce regressions.

Can I inline one-off abstractions to improve software quality automatically?

Inlining one-off abstractions is a core code simplification strategy to replace cleverness with clarity. It reduces unnecessary complexity and is verified by running tests, lints, and typechecks to maintain software quality.

When should I run code simplification in my software development workflow?

Code simplification should be run during post-implementation cleanup. After finishing a feature, executing this process ensures the codebase remains maintainable and free of unnecessary nesting or speculative elements.

Does code simplification replace cleverness with clarity in complex codebases?

Code simplification directly replaces cleverness with clarity by reducing deep nesting and inlining abstractions. This targeted approach streamlines the codebase and improves overall developer productivity while preserving functionality.

What are the limitations of automated code simplification for maintainability?

Automated code simplification is limited to post-implementation cleanup of specific elements like speculative code and one-off abstractions. It relies on existing tests, lints, and typechecks to verify that functionality is preserved during the reduction process.