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

my-code-write

Delegate writing predictable code to the `code-write` command, which has a cheaper writer model write the target file directly so the generated code never enters your context. Use for tests, scaffolding, fixtures, boilerplate, or a new file that copies an existing pattern, and when the user says "code write", "生成を委譲", or "雛形を書かせて". Do NOT use for design decisions, changes to public contracts or shared modules, edits inside an existing file that needs judgment, or logic with subtle correctness requirements.

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

Ynakatsuka/dotfiles
설치 방법 보기

포함된 파일(1)

  • SKILL.md3.6 KB

SKILL.md(원문)

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

Code Write Delegation

When to delegate

  • The result follows a pattern that an existing file already shows: a test for another module, a handler or model shaped like a sibling, a fixture, or a scaffold.
  • The spec can be stated completely up front, including the file path, the behavior, and the reference file to imitate.
  • The file is new or is owned entirely by this task, so a full rewrite is acceptable.

Write the code yourself when the change needs a design decision, touches a public contract, or must be woven into an existing file with judgment.

Command

code-write --spec "<complete spec>" --target <file> [--reference <file>]...
  • State the spec completely: what to cover, names to use, framework, and edge cases. The writer cannot ask questions.
  • Pass one or two reference files that show the exact pattern to copy. Each is sent verbatim.
  • The target must be inside the current working directory. An existing target is sent to the writer and rewritten as a whole.
  • Stdout carries the written path with its line count and a short summary; stderr carries progress. A non-zero exit means nothing usable was written. Report the error instead of retrying with the same input.

Collecting completion

  • This command is a shell process, not a spawn_agent task. Do not use wait_agent, clock.sleep, or shell sleep to wait for its result, and do not rely on a completion notification.
  • In Codex, when exec_command returns a session_id, collect output with write_stdin using that ID and empty chars. Use yield_time_ms: 1000 while waiting for this result; repeat while a session_id remains, until an exit_code and the final output arrive. The tool may enforce a longer minimum wait, but returns early when the process finishes.
  • functions.exec saying Script completed only ends the JavaScript wrapper. An inner session_id still needs collection. If the wrapper instead yields a running cell_id, resume it with functions.wait and yield_time_ms: 1000, then inspect the inner result.
  • Do independent work while the writer runs, but check its result at the next tool boundary. When its result is the only remaining dependency, keep collecting directly without an extra delay. Once the exit code and summary arrive, proceed to verification and stop waiting.
  • In Claude Code, collect a background Bash task with TaskOutput using its returned task ID; a finished task's output should be read immediately rather than waiting for another notification.
  • A target file appearing or changing is not proof of completion. Collect the command's exit status before reading, editing, or testing the target.

After the write

  • Run the narrowest relevant check on the target, such as the new test file or the linter, instead of reading the file to review it.
  • Confirm with git status that only the target changed.
  • When a check fails, read the failing region with a bounded range and fix it yourself, or re-run once with a more precise spec. Do not loop on the writer.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

my-agent

무료

Delegate tasks to an external CLI agent (OpenAI Codex, Google Gemini, or Claude Code) for second opinions or parallel execution. Use when the user explicitly mentions "codex", "gemini", or "claude" or asks to delegate work to one of them (e.g., "codexで実行", "codexに聞いて", "geminiで実行", "Geminiに聞いて", "claudeで実行", "Claudeに聞いて", "run with codex", "ask gemini", "ask claude"). Also use when the user mentions Claude's "fable" model alias for delegation or consultation (e.g., "fableで実行", "fableに相談", "Fableに聞いて", "ask fable"). Do NOT use for general coding tasks that don't mention codex, gemini, claude, or fable.

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

Ynakatsuka/dotfiles42026년 10월 18일 업데이트

my-bulk-read

무료

Delegate reading large or multiple files to the `bulk-read` command, which sends the files to a cheaper reader model and returns only its answer. Use when a question needs the content of a file over about 350 lines or of several files at once, when a PreToolUse guard denied an unbounded read, or when the user says "bulk read", "一括読み込み", or "まとめて読んで". Do NOT use for files you are about to edit, for subtle correctness reasoning such as concurrency bugs, or for short files that fit a bounded read.

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

Ynakatsuka/dotfiles42026년 10월 18일 업데이트

my-ccv

무료

Manage Claude Code Viewer (CCV): preview in-progress CCV changes on ccv-preview, register HTML artifacts, download files, or schedule jobs via CCV local API. Use when user asks for CCV preview, ccv-preview, browser visual QA, UI/UX validation, CCV artifacts, CCV file download, or CCV scheduler jobs. Treat preview/プレビュー as the CCV app preview service first; use artifacts only when the user explicitly asks for artifact/dashboard/report HTML. Do NOT use for generic web app previews outside CCV, production deployment, Cloudflare config, or Anthropic remote triggers.

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

Ynakatsuka/dotfiles42026년 10월 18일 업데이트

my-diagnose

무료

Disciplined diagnosis workflow for hard, intermittent, or multi-component bugs and performance regressions: inspect logs and existing evidence, build a feedback loop, test falsifiable hypotheses, instrument gaps, and verify the outcome. Use when the root cause is unclear, reproduction is unreliable, several causes or components are plausible, or performance has regressed. Do NOT use for obvious single-cause errors, straightforward configuration or syntax fixes, planned feature work, or broad architecture review. Diagnosis-only requests stop after reporting the root cause and evidence; apply a fix only when the user requested one.

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

Ynakatsuka/dotfiles42026년 10월 18일 업데이트

my-epic

무료

Manual-only orchestrator for medium-to-large software development. Turns a broad goal into PR-sized and operational nodes with verification gates, then coordinates approved execution across follow-up prompts. Activate only when the user explicitly invokes my-epic; once activated, keep orchestrating that epic for the rest of the session. Do NOT use for an uninvoked planning or implementation request, a single small bug fix, one obvious PR, pure code review, ordinary SDD work that fits in one spec/PR, or implementing an epic during the same first call that created it.

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

Ynakatsuka/dotfiles42026년 10월 18일 업데이트

my-handoff

무료

Hand off a task with only the context needed to continue in a fresh session. Use for "handoff", "引き継ぎ", "別セッションへ渡す", or "別マシンで続ける". The orca subcommand launches an independent Orca workspace or terminal tab; without it, produce a paste-ready prompt backed by a verified remote branch or PR. Do not launch sessions for capability questions or design requests.

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

Ynakatsuka/dotfiles42026년 10월 18일 업데이트

Ynakatsuka의 스킬 모두 보기

이 스킬의 문제 신고