alexbruno/dev-skills

code-simplification

Simplify code for human readability, clarity, and directness without changing behavior.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/alexbruno/dev-skills --skill code-simplification

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Code Simplification

Make code clean, direct, and easy for humans to read while preserving exact runtime behavior. Prefer straightforward, objective implementations over clever tricks or premature abstractions.

Core Principles

  1. Preserve Behavior Exactly: Inputs, outputs, side effects, error semantics, and edge-case guards must remain identical. Existing tests must pass without modification.
  2. Clarity Over Cleverness (and Over Brevity): The goal is human comprehension, not fewer lines. Never replace readable code with cryptic one-liners, nested ternaries, or dense chains.
  3. Direct Over Indirection: Do not take three hops to do something simple. Inline trivial single-use wrappers, pass-through helpers, and speculative abstractions that add ceremony without clarity.
  4. Chesterton's Fence: Before deleting or rewriting code that looks redundant or defensive, understand why it was written (check callers, tests, comments, or workflow/SPEC.md).

When to Apply

  • Right after a feature or bug fix works and tests pass, to clean up rough or over-complicated implementation details.
  • When functions have deep if/else nesting, long monolithic blocks, or unclear variable/method names.
  • When workflow/REVIEW.md flags readability, maintainability, or over-engineering issues.

What to Simplify

  • Flatten control flow: Replace deep if/else nesting with guard clauses and early returns.
  • Remove unnecessary indirection: Collapse pass-through functions, single-use factories, or redundant layers that hide simple operations.
  • Make logic linear and objective: Replace convoluted state flags or roundabout transformations with direct, step-by-step code.
  • Right-size functions: Break up overly long functions into cohesive, well-named units—only when each unit represents a clear step, not to fragment trivial code.
  • Use clear names, trim obvious noise: Rename vague identifiers so code is self-explanatory. Remove comments that merely restate the code, while preserving non-obvious why comments and existing docstrings.
  • Unify genuine duplication: When two blocks repeat the same logic, extract a single parameterized helper rather than maintaining parallel copies.

Guardrails (What NOT to Do)

  • Do not alter public APIs, return shapes, or error handling unless explicitly requested.
  • Do not refactor unrelated files outside the scope of the current change.
  • Do not remove edge-case checks (null, empty, boundary conditions) unless proven unreachable.

Verification

  1. Review the diff to confirm every change is simpler, cleaner, and strictly behavior-preserving.
  2. Run the relevant test suite, linter, and typechecker to verify all checks pass unchanged.
同じリポジトリから

関連する Skills

すべての Skills
alexbruno
コミュニティ

architect-worker

Role-based multi-agent software engineering pattern separating high-level architecture, specification, planning, and code review (Architect) from focused code implementation and verification (Worker). Use this skill whenever assigned the Architect or Worker role (in any language), or when coordinating work between planning/review agents and implementation agents via workflow/.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日
alexbruno
コミュニティ

changelog-management

Maintain and update a standardized root CHANGELOG.md following Keep a Changelog and Semantic Versioning. Use this skill to initialize or update changelog entries, categorize changes, prepare release cuts, and proactively prompt the user when notable changes warrant updating the changelog.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日
alexbruno
コミュニティ

code-review

Perform structured, multi-dimensional code reviews aligned with the spec-driven-workflow (workflow/SPEC.md, workflow/PLAN.md, workflow/REVIEW.md). Use this skill after implementing a feature or bug fix, before merging a PR, or when reviewing changes written by another agent or human.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日
alexbruno
コミュニティ

codebase-indexing

Index, synchronize, and query a project's codebase using CodeGraph and Repomix. Use this skill when exploring an unfamiliar repository, maintaining up-to-date code intelligence after edits, or setting up project indexing with .codegraph/ and Markdown-formatted Repomix snapshots.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日