simplify

Apply safe pre-commit fixes to changed engine code and report items for human review.

8|Updated Oct 11, 2023
One-click install
npx skills add https://github.com/jakildev/IrredenEngine --skill simplify-jakildev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify
Source: https://github.com/jakildev/IrredenEngine/tree/main/.claude/skills/simplify
Command: npx skills add https://github.com/jakildev/IrredenEngine --skill simplify-jakildev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Polishes the dirty working tree before committing — catching Irreden-Engine smells that would otherwise be flagged in review. It provides an automated pass that applies safe fixes and reports issues requiring human judgment, reducing back-and-forth during pull requests.

Core Features & Use Cases

  • Pre-commit cleanups across touched files, removing common issues like redundant debug logs, naming convention slips, and unsafe patterns.
  • Deterministic, inline fixes that do not alter program behavior, paired with a report for human review where necessary.
  • Works across the engine codebase (tick systems, ECS components, helpers) to shorten review cycles and speed up PRs.

Quick Start

Run the simplify skill before committing to automatically apply safe fixes and report items needing human review.

Frequently Asked Questions about simplify

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

FAQPage Schema
How do I automate code cleanup before committing changes to an ECS engine codebase?

To automate pre-commit code cleanup, this skill applies deterministic fixes to touched files across ECS engine modules, safely resolving naming slips and dead code while outputting a structured review report.

What is a safe pre-commit refactoring pass for engine modules?

A safe pre-commit refactoring pass applies inline edits that correct debug logs and naming conventions across engine modules without altering runtime behavior, generating a summary of issues for human review.

Can I use this to remove debug logs and dead code from touched files only?

Yes, you can use it to scope cleanup to touched files only, automatically removing redundant debug logs and dead code while flagging unsafe patterns that require manual judgment.

Does this pre-commit cleanup tool modify runtime behavior when fixing code smells?

No, this pre-commit cleanup tool enforces deterministic inline edits that specifically do not alter runtime behavior, ensuring safe code cleanup while reporting complex issues separately.

What's the best way to shorten review cycles for Irreden-Engine codebase pull requests?

The best way to shorten review cycles is running an automated pre-commit pass that catches engine code smells, applies safe fixes, and reports items needing human judgment before submitting.

When should I not rely on automated pre-commit cleanup for ECS components?

You should not rely on it when issues require human judgment, as the skill only applies deterministic edits and explicitly reports complex unsafe patterns in per-entity getComponent usage for manual review.