s-hiraoku/claude-harnesses · Archived

simplify

Review changed code on the current branch for reuse, clarity, and dead complexity, then propose or apply minimal cleanup without changing behavior.

First seen Jun 13, 2026

Installation

$ npx skills add s-hiraoku/claude-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/claude-harnesses · top by installs.

npx skills add s-hiraoku/claude-harnesses

Browse all from s-hiraoku/claude-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 Declared
Cursor Not declared
Codex Not 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 1
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,464 B
  • docs SUMMARY.md 163 B

History

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

SKILL.md

Simplify

Use this workflow after a feature is functionally complete but before review or merge, to remove avoidable complexity introduced during implementation.

Workflow

  1. List changed files: git diff origin/main...HEAD --stat and git diff origin/main...HEAD --name-only.
  2. For each meaningful file, ask:

- Is there an existing helper, type, or constant in the codebase that does this already? Search before adding. - Are there abstractions or layers that the change does not actually need yet? - Is there error handling for cases that cannot occur? - Are there comments restating what the code already says? - Are there unused variables, imports, or branches?

  1. Apply minimal, behavior-preserving cleanups. Do not rewrite working code for stylistic reasons.
  2. Re-run targeted tests for each touched module to confirm behavior is unchanged.

Constraints

  • Never introduce new abstractions during simplify — that is a separate refactor task.
  • Preserve public APIs and observable behavior exactly.
  • If a cleanup is risky, propose it in the final report instead of applying it.

Final Report

Include:

  • files cleaned up
  • specific reductions (lines removed, helpers reused)
  • tests run and result
  • proposals not applied (with reasoning)