improve

Name: improve
Author: owainlewis

238stars46forks

How to install improve?

owainlewis/blueprint/improve

$npx -y skills add owainlewis/blueprint --skill improve

Installs into the current project.

Summary

Improves existing code without changing intended behavior by simplifying structure, removing duplication and dead code, clarifying names, and reducing unnecessary abstractions. Use when the user asks to improve, simplify, clean up, refactor, reduce complexity, remove duplication,

Files · 1

View on GitHub

SKILL.md

1	# Improve
2
3	## Workflow
4
5	1. Identify the target from the request, current diff, or recently changed code.
6	2. Read the target, its tests, and relevant surrounding code. Establish the behavior that must not change.
7	3. Look for unnecessary complexity, duplication, dead code, weak names, awkward boundaries, and abstractions that cost more than they help.
8	4. Make focused improvements by deleting, deduplicating, renaming, simplifying, extracting, or inlining.
9	5. Preserve public interfaces, data shapes, errors, and user-visible behavior unless the user explicitly asks to change them.
10	6. Run the relevant tests and checks. Report what improved, what behavior was preserved, and the evidence.
11
12	## Boundaries
13
14	- Do not add product scope or absorb unrelated cleanup.
15	- Prefer a few clear edits over a broad rewrite.
16	- Preserve behavior even when a redesign would be easier.

People who liked this also viewed

6 picks

Type

improve

238stars46forks

View on GitHub

How to install improve?

owainlewis/blueprint/improve

$npx -y skills add owainlewis/blueprint --skill improve

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Improve
2
3	## Workflow
4
5	1. Identify the target from the request, current diff, or recently changed code.
6	2. Read the target, its tests, and relevant surrounding code. Establish the behavior that must not change.
7	3. Look for unnecessary complexity, duplication, dead code, weak names, awkward boundaries, and abstractions that cost more than they help.
8	4. Make focused improvements by deleting, deduplicating, renaming, simplifying, extracting, or inlining.
9	5. Preserve public interfaces, data shapes, errors, and user-visible behavior unless the user explicitly asks to change them.
10	6. Run the relevant tests and checks. Report what improved, what behavior was preserved, and the evidence.
11
12	## Boundaries
13
14	- Do not add product scope or absorb unrelated cleanup.
15	- Prefer a few clear edits over a broad rewrite.
16	- Preserve behavior even when a redesign would be easier.

People who liked this also viewed

6 picks

Type