Communityコーディング&開発github.com

everyinc/ce-simplify-code

最近変更されたコードを明確さ、再利用性、品質、効率のために簡素化・洗練し、動作を維持します。

ce-simplify-code とは?

このスキルは、AIエージェント(例:Claude Code、Cursor、Codex)が最近変更されたコードを自動的に解析し、読みやすさ、再利用性、品質、パフォーマンスを向上させるためにリファクタリングするためのものです。コードの外部動作(ビヘイビア)は一切変更せず、可読性の向上、重複の排除、より効率的なアルゴリズムへの置き換え、命名規則の改善などを安全に実行します。主にバージョン管理システム(Git)と連携し、未コミットの変更や直近のコミットを対象とします。開発者はこのスキルを使用することで、手動リファクタリングの負担を減らし、コードベースの一貫性とメンテナンス性を高めることができます。Claude Code、Cursor、Codexなどの主要なAIエージェントプラットフォームで動作するよう設計されています。

対応~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/everyinc/compound-engineering-plugin/tree/main/skills/ce-simplify-code

Installed? Explore more コーディング&開発 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

お気に入りのAIに質問する

このエージェントスキルを事前に読み込んだ状態で新しいチャットを開きます。

ドキュメント

ce-simplify-code は何をしますか?

最近変更されたコードを明確さ、再利用性、品質、効率のために簡素化・洗練し、動作を維持します。

概要

このスキルは、コードベース内の最近変更された部分を自動的に特定し、以下の側面を改善するためのリファクタリングを提案/適用します:

  • 明確さ: 変数名、関数名、コメントをより説明的に改善
  • 再利用性: コードをよりモジュール化し、重複を排除
  • 品質: コードの一貫性を向上させ、アンチパターンを除去
  • 効率: パフォーマンスを改善するリファクタリングを適用

重要な制約: 元のコードの外部動作は完全に保持されます。このスキルは純粋にリファクタリングのみを行い、機能の追加や変更は行いません。

対応プラットフォーム

  • Claude Code
  • Cursor
  • Codex
  • その他の主要なAIエージェント

使用方法

このスキルは、主に以下のようなシナリオで使用します:

  1. コードレビュー前: 変更をコミットする前にコードを自動的に洗練
  2. 開発サイクル中: 機能実装後、コードの品質を確保
  3. レガシーコード改善: 古いコードを段階的に改善

基本的な使い方

# 直近の変更を解析し、改善案を表示
# (AIエージェントの設定に依存)

動作詳細

このスキルは以下のプロセスに従います:

  1. 変更されたファイルを特定(Git差分を使用)
  2. 各変更に対して、動作を変えずに改善できる箇所を分析
  3. 改善案を生成し、説明とともに提示
  4. ユーザーの承認後、変更を適用

設定

特別な設定は必要ありません。このスキルは事前に定義されたルールに基づいて動作します。

注意事項

  • 外部動作を変更しないことを保証しますが、複雑なコードの場合は変更後にテストを実行することを推奨
  • 非常に大きな変更(多くのファイルにまたがる)の場合は、段階的に適用することを推奨
  • 特定のコーディングスタイルや規約がある場合は、事前にAIエージェントに指示してください

ライセンス

MIT License

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

everyinc/ce-agent-native-architecture

Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.

everyinc/ce-agent-native-audit

Run comprehensive agent-native architecture review with scored principles

everyinc/ce-brainstorm

Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.

everyinc/ce-clean-gone-branches

Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.

everyinc/ce-code-review

Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. In interactive mode it applies safe, verified fixes and commits them when the working tree is clean (it never pushes); in mode:agent it reports only and the caller applies. Use when reviewing code changes before creating a PR.

everyinc/ce-commit

Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.

everyinc/ce-commit-push-pr

Commit, push, and open a PR with an adaptive, value-first description that scales in depth with the change. Use when the user says "commit and PR", "ship this", "create a PR", or "open a pull request". Also handles description-only flows ("write a PR description", "rewrite the PR body", "describe this PR") without committing or pushing.

everyinc/ce-compound

Document a recently solved problem to compound your team's knowledge or CONCEPTS.md, the project's shared domain vocabulary.

everyinc/ce-compound-refresh

Refresh stale learning and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, or deleting drifted ones. Use when the user asks to "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", or "consolidate overlapping docs", or when ce-compound flags an older doc as superseded. Do not trigger for general refactor, debugging, or code-review work unless the user has explicitly pointed at docs/solutions/.

everyinc/ce-debug

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.

everyinc/ce-demo-reel

Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI features, or any work with observable behavior that benefits from visual proof. Also use when asked to add a demo, record a GIF, screenshot a feature, show what changed visually, create a demo reel, capture evidence, add proof to a PR, or create a before/after comparison.

everyinc/ce-dhh-rails-style

This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.

everyinc/ce-doc-review

Review requirements or plan documents using parallel persona agents that surface role-specific issues. Use when a requirements document or plan document exists and the user wants to improve it.

everyinc/ce-frontend-design

Build web interfaces with genuine design quality, not AI slop. Use for any frontend work - landing pages, web apps, dashboards, admin panels, components, interactive experiences. Activates for both greenfield builds and modifications to existing applications. Detects existing design systems and respects them. Covers composition, typography, color, motion, and copy. Verifies results via screenshots before declaring done.

everyinc/ce-gemini-imagegen

This skill should be used when generating and editing images using the Gemini API (Nano Banana Pro). It applies when creating images from text prompts, editing existing images, applying style transfers, generating logos with text, creating stickers, product mockups, or any image generation/manipulation task. Supports text-to-image, image editing, multi-turn refinement, and composition from multiple reference images.

everyinc/ce-ideate

Generate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea.

everyinc/ce-optimize

Run metric-driven iterative optimization loops -- define a measurable goal, run parallel experiments, measure each against hard gates or LLM-as-judge scores, keep improvements, and converge on the best solution. Use when optimizing clustering quality, search relevance, build performance, prompt quality, or any measurable outcome that benefits from systematic experimentation.

everyinc/ce-plan

Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from breakdown. Also deepens existing plans with interactive sub-agent review. Use when the user says 'plan this', 'create a plan', 'how should we build', 'break this down', or when a brainstorm doc is ready for planning. Use 'deepen the plan' or 'deepening pass' for the deepening flow. For exploratory requests, prefer ce-brainstorm first.

everyinc/ce-polish-beta

[BETA] Start the dev server, open the feature in a browser, and iterate on improvements together.

everyinc/ce-product-pulse

Generate a time-windowed pulse report on what users experienced and how the product performed - usage, quality, errors, signals worth investigating. Use when the user says 'run a pulse', 'show me the pulse', 'how are we doing', 'weekly recap', 'launch-day check', or passes a time window like '24h' or '7d'. Configures via .compound-engineering/config.local.yaml and saves reports to docs/pulse-reports/.

関連スキル