Community코딩 & 개발github.com

everyinc/ce-clean-gone-branches

원격 트래킹 브랜치가 사라진 로컬 브랜치를 정리합니다. 사용자가 "브랜치 정리", "삭제된 브랜치 제거", "로컬 브랜치 가지치기", "정리" 등을 요청할 때 사용합니다. 연결된 워크트리도 함께 제거합니다.

ce-clean-gone-branches란 무엇인가요?

이 스킬은 원격 저장소에서 더 이상 존재하지 않는(즉, 'gone' 상태인) 로컬 브랜치를 자동으로 식별하고 안전하게 제거합니다. 개발자가 수동으로 하나씩 확인하고 삭제하는 번거로움을 없애주며, 브랜치 정리 작업을 효율적으로 수행할 수 있게 합니다. Git 명령어 `git branch -vv`를 사용하여 원격 트래킹 브랜치가 없는 로컬 브랜치를 찾아내고, 각 브랜치에 연결된 Git 워크트리(worktree)가 있다면 해당 워크트리도 함께 제거합니다. Claude Code, Cursor, Codex 등 AI 기반 개발 도구와 함께 사용하기에 적합하며, 사용자가 '브랜치 정리', '삭제된 브랜치 제거' 등의 자연어 명령을 내리면 즉시 실행됩니다. 주요 기능으로는 여러 개의 'gone' 브랜치를 한 번에 정리할 수 있는 일괄 처리와, 각 삭제 작업에 대한 상세한 로그 출력이 포함되어 있습니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/everyinc/compound-engineering-plugin/tree/main/skills/ce-clean-gone-branches

Installed? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

원본 보기→모든 스킬 둘러보기

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

문서

ce-clean-gone-branches은(는) 무엇을 하나요?

원격 트래킹 브랜치가 사라진 로컬 브랜치를 정리합니다. 사용자가 "브랜치 정리", "삭제된 브랜치 제거", "로컬 브랜치 가지치기", "정리" 등을 요청할 때 사용합니다. 연결된 워크트리도 함께 제거합니다.

사용 방법

이 스킬은 다음과 같은 자연어 명령으로 트리거됩니다:

  • "브랜치 정리"
  • "삭제된 브랜치 제거"
  • "로컬 브랜치 가지치기"
  • "정리"
  • "원격에 없는 로컬 브랜치 삭제"

동작 방식

  1. git branch -vv 명령어를 실행하여 모든 로컬 브랜치와 해당 원격 트래킹 브랜치 상태를 확인합니다.
  2. 원격 트래킹 브랜치가 'gone' 상태인 로컬 브랜치를 식별합니다.
  3. 각 식별된 브랜치에 대해 연결된 Git 워크트리가 있는지 확인합니다.
  4. 발견된 각 브랜치에 대해 다음 작업을 수행합니다:
    • 연결된 워크트리가 있다면 먼저 제거합니다.
    • 그런 다음 로컬 브랜치를 삭제합니다.
  5. 모든 작업에 대한 상세 로그를 출력합니다.

예시

# 사용자가 '브랜치 정리' 요청 시 실행되는 내부 로직 (참고용)
# 스킬이 자동으로 처리하므로 직접 실행할 필요 없음

지원 플랫폼

  • Claude Code
  • Cursor
  • Codex
  • 기타 AI 기반 개발 도구

주의 사항

  • 삭제된 브랜치는 복구할 수 없으므로, 중요한 작업이 포함된 브랜치는 미리 백업하시기 바랍니다.
  • 현재 체크아웃된 브랜치는 삭제되지 않습니다.
  • 이 스킬은 로컬 브랜치만 정리하며, 원격 브랜치에는 영향을 미치지 않습니다.

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

everyinc/ce-proof

Publish, view, comment on, and edit markdown via Proof (proofeditor.ai) — create a shareable doc, read a shared doc, and make comment/suggestion/block edits over its API. Use when the user says "view this in proof", "share to proof", "publish to proof", or wants a shareable markdown surface for a spec, plan, or draft, including publish handoffs from ce-brainstorm, ce-ideate, or ce-plan. Do not trigger on "proof" meaning evidence, math proofs, proof-of-concept, or "proofread this".

관련 스킬

steipete/bluebubbles

Send and manage iMessages via BlueBubbles, including attachments, tapbacks, edits, replies, and groups.

community

steipete/eightctl

Control Eight Sleep pods (status, temperature, alarms, schedules).

community

steipete/blucli

BluOS CLI (blu) for discovery, playback, grouping, and volume.

community

steipete/bear-notes

Create, search, and manage Bear notes via grizzly CLI.

community

steipete/camsnap

Capture frames or clips from RTSP/ONVIF cameras.

community

steipete/gifgrep

Search GIF providers with CLI/TUI, download results, and extract stills/sheets.

community
← More 코딩 & 개발 skills