Simplify Code

Simplify uncommitted code changes with behavior-preserving fixes.

Updated Dec 27, 2018
One-click install
npx skills add https://github.com/segersniels/dotfiles --skill simplify-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Simplify Code
Source: https://github.com/segersniels/dotfiles/tree/main/.codex/skills/simplify
Command: npx skills add https://github.com/segersniels/dotfiles --skill simplify-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Simplify and refine uncommitted changes by removing slop, fixing patterns, and improving clarity while keeping behavior unchanged.

Core Features & Use Cases

  • Structural cleanup: remove noisy diffs and questionable patterns to improve maintainability.
  • Style and readability improvements: clarify intent without changing functionality.
  • Use Case: when a patch contains messy revisions, run this to produce a clear, review-friendly diff.

Quick Start

Review the current uncommitted changes and produce a cleaner, behavior-preserving patch ready for commit.

Frequently Asked Questions about Simplify Code

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

FAQPage Schema
How do I clean up uncommitted code changes before committing?

To clean up uncommitted code changes, you can automate the simplification of your diff to remove noisy patterns and improve clarity while preserving the original behavior. This process refines modified files into a review-ready patch.

What is the best way to refactor a messy diff for code review?

Refactoring a messy diff for code review involves applying structural cleanup and style improvements to clarify intent without changing functionality. This ensures the patch is deterministic, safe, and easy for reviewers to follow.

Does automated code simplification alter program behavior?

Automated code simplification does not alter program behavior. It focuses on improving readability, removing questionable patterns, and refining structure through small deterministic fixes while strictly maintaining the existing functionality.

How does a code review workflow spot style and clarity issues?

A code review workflow spots style and clarity issues by detecting the change scope, reading the full context, and identifying structural problems. It then applies small, deterministic fixes to produce a cleaner, behavior-preserving patch.

Can I apply best practices to uncommitted files automatically?

You can apply best practices to uncommitted files automatically by running a diff cleanup process. It guides the reviewer through scope detection and issue spotting to ensure repeatable, safe improvements across structure and style.