| name | code-simplify |
| kstack | true |
| description | Simplify changed code in a PR or branch for readability while preserving behavior. Use when the user asks to simplify code, reduce complexity, clean up a PR, or improve readability of recent changes. |
Code Simplify
Usage
- Simplify code in a specific PR (provide PR number)
- Simplify code in current branch vs parent branch (default)
Step 1: Gather Context
Determine the diff base branch, then gather the diff:
DIFF_BASE=$(gt parent --no-interactive 2>/dev/null || echo "main")
git --no-pager diff "$DIFF_BASE"...HEAD
Read all changed files in full to understand the complete context.
Before introducing a new helper or abstraction, search the surrounding package and shared utility directories (utils,
services, db/queries, component/common folders) for existing helpers with the same responsibility. Prefer reusing or
extending an existing helper; only create a new one when no match exists.
Step 2: Check Lint Complexity
Run the project's lint command and collect any cognitive complexity warnings in changed files. Each function that
exceeds the max allowed complexity becomes a mandatory refactor target in Step 3 — extract coherent logical sections
into well-named helpers until the score drops below the threshold.
Step 3: Identify Simplification Opportunities
Review every changed file. Go beyond fixing anti-patterns — actively simplify. Include any lint complexity violations
from Step 2 as additional targets.
Hard Constraints
- Avoid introducing
any types — even if it would reduce duplication or improve readability. Prefer duplicated code
over compromising type safety.
- No slop comments — do NOT add comments that restate what the code does (e.g.,
// Add to array,
// Return the result). Comments explaining "why" are fine.
- No unnecessary defensive code — don't add try/catch blocks or null checks that are abnormal for that area of the
codebase
For the full catalog of simplification patterns, see patterns.md.
Step 4: Make Changes
Refactor the code directly. For each file:
- Apply all simplifications that improve readability
- Preserve identical functionality — no behavior changes
- Bias toward clarity over cleverness
Step 5: Report
Summarize in 2-4 sentences:
- Which files were simplified
- What patterns were addressed
- Any files skipped and why
Project Context
Read context.md and apply it as additional project-specific constraints layered on top of this
workflow. If it does not exist, skip this section.
