code-simplifier
Simplifies and cleans up code by reducing complexity and removing unnecessary abstractions.
- License 许可
- MIT
- 所属仓库
- goffity/dev-km
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- code-simplifier
- context
- fork
- description
- Simplifies and cleans up code by reducing complexity and removing unnecessary abstractions.
- user-invocable
- false
02 资源文件 3
- 参考文档_meta.json282 B
- 参考文档SOURCE.md250 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Code Simplifier
Agent สำหรับ simplify code หลังจากเขียนเสร็จ - ลด complexity และทำให้ code อ่านง่ายขึ้น
Purpose
- ลด code complexity
- Remove unnecessary abstractions
- Simplify logic และ control flow
- ลด duplication
- ทำให้ code อ่านง่ายและ maintain ง่าย
When to Use
- หลังจากเขียน code เสร็จ
- เมื่อ code ดู complex เกินไป
- ก่อน commit เพื่อ clean up
- เมื่อต้องการ refactor
Instructions
Step 1: Identify Target Files
git diff --name-only HEAD
Step 2: Analyze Complexity
For each file, check for:
-
Over-engineering:
- Unnecessary abstractions
- Too many layers of indirection
- Premature optimization
- Over-generalization
-
Code Smells:
- Functions longer than 20 lines
- Deep nesting (> 3 levels)
- Too many parameters (> 4)
- Duplicate code blocks
-
Unnecessary Patterns:
- Design patterns where simple code works
- Complex inheritance when composition is simpler
- Callbacks when async/await is cleaner
Step 3: Simplification Strategies
| Problem | Solution |
|---|---|
| Long function | Extract smaller functions |
| Deep nesting | Early returns, guard clauses |
| Complex conditionals | Switch/match or lookup tables |
| Duplicate code | Extract shared function |
| Over-abstraction | Inline simple abstractions |
| Too many helpers | Consolidate or inline |
Step 4: Apply YAGNI Principle
- Remove code for "future use"
- Remove unused parameters
- Remove commented-out code
- Remove empty/placeholder functions
Step 5: Readability Improvements
- Use descriptive variable names
- Add whitespace for clarity
- Group related code together
- Simplify boolean expressions
- Use early returns
Output Format
## Code Simplification Report
**Files Analyzed:** N files
**Simplifications Found:** X items
---
### File: [filename]
#### Before
```[language]
// Complex code
After
// Simplified code
Why: Explanation of the simplification
Summary of Changes
| Type | Count |
|---|---|
| Functions simplified | X |
| Abstractions removed | Y |
| Duplicates merged | Z |
| Lines reduced | N |
## Guidelines
### DO Simplify:
- 3 similar lines → 1 loop or function
- Nested if-else → switch or early returns
- Complex boolean → named variable
- Callback hell → async/await
### DON'T Over-Simplify:
- Don't remove necessary error handling
- Don't merge unrelated functions
- Don't sacrifice clarity for brevity
- Don't remove useful abstractions
04 同仓库更多 Skills
wait-what
Stop. That last message did not land: re-pitch it.
tdd
Test-driven development loop (red-green-refactor) with commit-based phase state and Jira traceability. Use when the user wants to build a feature or fix a bug test-first, mentions "tdd", "red-green-refactor", or "test-first". Replaces the tdg plugin — combines its commit/phase discipline with seam-based test quality rules from kb Testing Standards.
td
Creates post-task retrospectives with Before/After context and session documentation.
summary
Generates weekly or monthly session summaries from retrospectives and activity logs.
share
Shares knowledge across projects by copying to shared-knowledge directory with cross-project metadata.
session-analyzer
Analyzes git changes and creates retrospective drafts with Before/After context.