본문으로 건너뛰기
cccskills
무료GitHub에 공개

execute

Carry an agreed development task through implementation and verification. Make small changes that follow existing patterns, divide independent work when useful, and report changed files, evidence that the code works, and any remaining issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Carry an approved task through to working, verified code

설치 방법 보기

이럴 때 유용합니다

  • Implementing an agreed feature
  • Making a small code fix and verifying it
  • Splitting independent development tasks
  • Completing a long-running implementation task

포함된 파일(1)

  • SKILL.md2.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Execute

Use this skill when the work is understood and the job is to build it.

This is the canonical execution workflow. autopilot, ralph, ultragoal, ultrapilot, pipeline, and swarm route here.

Goal

Take a task from agreed intent to working code, with evidence that it works.

Workflow

  1. Confirm the task is clear enough to build. If it is not, plan first.
  2. Break the work into independent units; run genuinely independent units in parallel.
  3. Implement the smallest correct change per unit, reusing existing utilities and patterns.
  4. Verify as you go, not only at the end.
  5. Report what changed, what was verified, and what remains.

Scale

Match the machinery to the task:

  • Single unit — implement directly, verify, done.
  • Several independent units — delegate to executor agents in parallel.
  • Long-running or unbounded — keep a durable task list and continue until the list is empty.
  • Needs coordinated parallel workers — use team.

Do not spin up coordination for work that one focused pass would finish.

Rules

  • Prefer deletion over addition when behavior is preserved.
  • Do not add dependencies without an explicit request.
  • Keep diffs small and reversible.
  • Work on two tracks at once: finish the task in front of you, and notice what would make the next task easier or safer — the second track is a proposal, not a detour.
  • No workarounds: a deviation from convention that only unblocks you today (a skipped check, a hard-coded value, a manual step) is fixed or flagged before feature work lands on top of it — it never silently becomes the norm.
  • Before asserting what a skill or protocol does, or skipping one of its steps, read its source — summaries are for finding it, not for standing in for it.
  • Placeholder TODOs, test.skip, and stub tests are blockers, not progress.
  • Authoring and approval are separate passes — do not self-approve; hand off to review or verify.

Completion

Before claiming done:

  • No pending tasks
  • Tests pass, or failures are reported plainly
  • Verification evidence collected

Output

  • Files changed
  • What was implemented
  • Evidence it works
  • What is still open

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Write or revise instructions, specifications, tickets, and skill files so an agent can act without prior chat history. Make rules checkable, explain their reasons, define completion criteria, and keep authoritative information in one place.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Clarifying instructions in CLAUDE.md
  • Making specifications and tickets actionable
  • Adding completion criteria to skill procedures
Yeachan-Heo/oh-my-claudecode4만2026년 10월 21일 업데이트

Simplify bloated AI-generated code by removing dead code, duplicated logic, and unnecessary layers while checking that existing behavior stays intact. Use a limited cleanup scope, verify changes with relevant checks, or request a review without edits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Removing duplicate logic and unused code
  • Simplifying unnecessary wrappers without changing behavior
  • Cleaning up only a specified set of changed files
Yeachan-Heo/oh-my-claudecode4만2026년 10월 21일 업데이트

Review module relationships and change history to identify structural improvements in a codebase. Receive ranked candidates with file references, suggested changes, and risks, plus a recommendation for where to start, without modifying code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing architecture after a batch of changes
  • Investigating changes that touch too many files
  • Prioritizing structural improvements
Yeachan-Heo/oh-my-claudecode4만2026년 10월 21일 업데이트

ask

무료

Send questions, review requests, or implementation tasks to a supported local AI command-line tool through one shared command. The wrapper handles provider-specific options and saves the result as a Markdown file for later reference.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Requesting a security review of a patch
  • Seeking UX suggestions for a user flow
  • Drafting an implementation plan for an issue
Yeachan-Heo/oh-my-claudecode4만2026년 10월 21일 업데이트

Turn an unclear idea into linked decision tickets on a repository’s issue tracker. Work through one decision per session, record outcomes and dependencies, and prepare a brief defining the objective, scope, and exclusions for delivery.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Clarifying the destination of an early idea
  • Mapping decisions and their dependencies
  • Resuming unresolved decisions across sessions
Yeachan-Heo/oh-my-claudecode4만2026년 10월 21일 업데이트

autopilot

무료

Turn a short product idea into working code through requirements analysis, technical planning, implementation, testing, and review. It coordinates agents across these stages, fixes detected problems, and reports assumptions that still need a human decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Building a product from a short idea
  • Creating a bookstore inventory API
  • Developing a habit-tracking command-line tool
Yeachan-Heo/oh-my-claudecode4만2026년 10월 21일 업데이트

Yeachan-Heo의 스킬 모두 보기

이 스킬의 문제 신고