s-hiraoku/codex-harnesses · Archived

simplify

Remove avoidable complexity from changed code while preserving behavior exactly.

First seen Jun 13, 2026

Installation

$ npx skills add s-hiraoku/codex-harnesses --skill simplify

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from s-hiraoku/codex-harnesses · top by installs.

npx skills add s-hiraoku/codex-harnesses

Browse all from s-hiraoku/codex-harnesses

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 2
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents codex

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,180 B
  • docs SUMMARY.md 96 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Simplify

Use this workflow after a feature or bug fix works, but before review or release, to reduce unnecessary complexity introduced during the change.

Workflow

  1. Identify the changed files and public behavior that must remain unchanged.
  2. For each non-trivial changed file, check whether the change added:

- helpers used only once - abstractions without a second caller - validation for impossible states - unused imports, variables, branches, flags, or configuration - comments that restate code instead of explaining intent - duplicated logic that an existing local helper already handles

  1. Search before introducing or keeping a helper; prefer established project patterns.
  2. Apply minimal cleanup only when behavior is clearly unchanged.
  3. Leave risky cleanup as a proposal instead of applying it.
  4. Re-run targeted tests for each touched area.

Final Report

Include:

  • files simplified
  • specific complexity removed
  • behavior-preservation checks run
  • cleanup proposals intentionally left unapplied
  • residual risks