Community코딩 & 개발github.com

everyinc/ce-simplify-code

최근에 변경된 코드를 동작은 유지하면서 명확성, 재사용성, 품질 및 효율성을 위해 단순화하고 개선합니다.

ce-simplify-code란 무엇인가요?

이 스킬은 최근에 변경된 코드를 분석하여 동작을 변경하지 않으면서 더 명확하고, 재사용 가능하며, 효율적인 코드로 단순화 및 개선하는 데 사용됩니다. Cursor, Claude Code와 같은 AI 에이전트 플랫폼에서 코드 리팩토링을 자동화하여 개발자의 수작업을 줄여줍니다. 스킬은 변경된 코드 영역을 식별하고, 불필요한 복잡성을 제거하며, 코드 품질 메트릭(가독성, 유지보수성, 성능)을 향상시키는 변환을 적용합니다. 주로 git diff를 통해 변경 사항을 파악하고, 각 코드 덩어리에 대해 단순화 규칙을 적용한 후 변경 사항을 적용합니다. 이 스킬은 버그 수정이나 기능 추가 시 기존 동작을 보존하면서 코드베이스의 건강성을 유지하려는 팀에 특히 유용합니다.

지원 대상~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은(는) 무엇을 하나요?

최근에 변경된 코드를 동작은 유지하면서 명확성, 재사용성, 품질 및 효율성을 위해 단순화하고 개선합니다.

설명

이 스킬은 개발자가 최근에 수정한 코드 영역을 자동으로 분석하고 리팩토링합니다. 주된 목표는 코드의 동작을 변경하지 않으면서 가독성을 높이고 중복을 제거하며 성능을 최적화하는 것입니다.

사용 방법

  1. AI 에이전트와의 대화에서 이 스킬을 호출합니다.
  2. 스킬은 현재 브랜치의 최근 커밋 또는 스테이징된 변경 사항을 분석합니다.
  3. 분석 결과를 바탕으로 코드 단순화 및 개선 제안을 생성합니다.
  4. 사용자는 제안된 변경 사항을 검토하고 적용할 수 있습니다.

지원 플랫폼

  • Claude Code
  • Cursor
  • Codex CLI
  • 기타 AI 에이전트 플랫폼

주요 기능

  • 명확성 향상: 복잡한 조건문, 긴 함수, 이해하기 어려운 로직을 단순화합니다.
  • 재사용성 개선: 중복 코드를 제거하고 공통 로직을 함수나 모듈로 추출합니다.
  • 품질 개선: 코드 스타일 일관성, 네이밍 규칙, 에러 처리 패턴을 개선합니다.
  • 효율성 최적화: 불필요한 연산, 중복 호출, 비효율적인 데이터 구조를 최적화합니다.

동작 방식

  1. git diff를 사용하여 최근 변경된 코드 영역을 식별합니다.
  2. 각 변경된 코드 덩어리에 대해 단순화 규칙을 적용합니다.
  3. 각 제안된 변경 사항에 대한 설명을 제공합니다.
  4. 사용자 승인 후 변경 사항을 적용합니다.

주의 사항

  • 이 스킬은 코드의 동작을 변경하지 않습니다. 모든 리팩토링은 동작 보존을 원칙으로 합니다.
  • 복잡한 리팩토링은 여러 번에 걸쳐 수행하는 것이 좋습니다.
  • 항상 변경 사항을 검토하고 테스트한 후 적용하세요.

예시

# 리팩토링 전
def process_data(data):
    result = []
    for item in data:
        if item['type'] == 'a':
            result.append(item['value'] * 2)
        elif item['type'] == 'b':
            result.append(item['value'] * 3)
    return result

# 리팩토링 후
def process_data(data):
    multipliers = {'a': 2, 'b': 3}
    return [item['value'] * multipliers[item['type']] for item in data if item['type'] in multipliers]

라이선스

이 스킬은 MIT 라이선스 하에 배포됩니다.

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/.

관련 스킬