本文へ移動
cccskills
無料GitHub で公開

code-simplification

Simplifies recently changed or explicitly scoped code while preserving observable behavior, error semantics, side effects, ordering, and public contracts. Use for readability cleanup, dead-code removal, reducing nesting, eliminating redundant wrappers, or making an implementation easier to maintain. Not for architecture redesign, new behavior, speculative cleanup, or a refactor without an adequate safety net.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md2.0 KB
  • agents/openai.yaml217 B
  • references/simplification-checks.md653 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Code Simplification

Optimize comprehension and locality, not line count or personal style.

Establish the invariant

Identify callers, outputs, errors, side effects, ordering, performance-sensitive behavior, and tests. Read history or comments when a strange construct may be a compatibility fence. If behavior is unclear, stop and use codebase-orientation or root-cause-debugging before editing.

Find earned simplifications

Prefer concrete signals: duplicated policy, deep conditional nesting, stale branches, misleading names, pass-through wrappers, abstractions with no current variation, repeated conversions, and comments that restate code. Preserve abstractions that own policy, isolate volatility, or provide a real test seam.

Use simplification-checks.md to classify each candidate.

Change incrementally

  1. Make one coherent simplification.
  2. Run focused behavior proof without weakening existing assertions.
  3. Inspect the diff for hidden contract or error changes.
  4. Continue only while each step improves comprehension.

Use a codemod or AST-aware transformation for large mechanical rewrites. Keep feature work and broad cleanup separate unless the simplification is required to implement the authorized behavior safely.

Completion condition

Behavioral proof passes unchanged, the diff stays inside the stated scope, no error handling or compatibility path was accidentally removed, and the result is demonstrably easier to understand in its local codebase context.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and runs reproducible evaluations for AI agents, prompts, tools, skills, and model-backed workflows using realistic datasets, isolated baselines, objective assertions, rubric grading, trajectory analysis, cost/latency tracking, and regression comparison. Use when measuring agent quality, optimizing skill triggering, comparing prompts or models, or gating an AI feature release. Not for ordinary deterministic unit tests.

日本語の概要は準備中です。原文の説明を表示しています。

thiientv/godmode962026年8月26日 更新

Designs or reviews HTTP, REST, GraphQL, RPC, CLI, webhook, event, and service interfaces with explicit inputs, outputs, errors, compatibility, idempotency, pagination, authentication, versioning, and observability. Use when introducing or changing an API or cross-component contract. Not for internal implementation details with no boundary or for debugging one API failure; use root-cause-debugging there.

日本語の概要は準備中です。原文の説明を表示しています。

thiientv/godmode962026年8月26日 更新

Reviews an existing codebase for structural friction, unclear ownership, leaky or shallow interfaces, excessive coupling, misplaced state, poor testability, and risky dependency direction, then prioritizes evidence-backed improvement candidates. Use for architecture audits, modularization, modernization, or recurring cross-cutting change pain. Not for designing one new interface, simplifying a local function, or fixing a reproduced bug.

日本語の概要は準備中です。原文の説明を表示しています。

thiientv/godmode962026年8月26日 更新

Validates a running application, CLI, API, service, or generated artifact as a user or operator against a prewritten observable behavior contract while remaining source-blind. Use for acceptance checks, runtime proof, anti-fake probes, release smoke tests, or an independent companion to code review. Not for source-quality findings, root-cause diagnosis, or visual design judgment outside the contract.

日本語の概要は準備中です。原文の説明を表示しています。

thiientv/godmode962026年8月26日 更新

Closes a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.

日本語の概要は準備中です。原文の説明を表示しています。

thiientv/godmode962026年8月26日 更新

Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a browser or for backend-only tests.

日本語の概要は準備中です。原文の説明を表示しています。

thiientv/godmode962026年8月26日 更新

thiientv のスキルをすべて見る

このスキルの問題を報告する