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

do

Carry out a task from work/tasks/ — the implementer agent writes the change, the reviewer agent checks it, findings go back for fixing; the user gets the summary and commits.

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

kozii-d/hover-translate스타 25(GitHub 25 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.4 KB

SKILL.md(원문)

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

Carry out task $0. You orchestrate; the work is done by two subagents, each in a clean context: implementer and reviewer (.claude/agents/). Talk to the user in Russian.

1. Start

  • Find work/tasks/$0-*.md. None, or its status in work/backlog.md is not todo / in progress — stop and tell the user.
  • git status --short: uncommitted changes that are not this task's are the user's — mention them; the agents must not touch them.
  • Set the status in work/backlog.md to in progress.

2. Implementer

Start the implementer agent. Its prompt: the task file's path, and nothing else — the rest it reads itself. Wait for it to finish.

When it returns a question instead of a result: ask the user (with the options it gave), then send the answer to the same agent with SendMessage, so it keeps its context. If resuming fails, write the answer into the task file (a «Решения по ходу» section) and start a new implementer.

3. Reviewer

When the implementer is done, start the reviewer agent with the task file's path.

  • Findings marked [исправить] → send them to the same implementer with SendMessage; when it is done, send "second round" to the same reviewer. At most two rounds. What remains after that goes to the user.
  • Findings marked [решить] and the implementer's "not agreed" answers do not go back: they go to the user.

4. Clean up

rm -rf work/runs/$0, run from the repository root, once both agents are finished. Nothing else in work/ is deleted.

5. Report to the user

In Russian, short:

  1. What was done — 5–10 lines.
  2. All of the reviewer's findings and what happened to each: fixed / the implementer disagreed (why) / waits for your decision.
  3. Manual checks — from «Ручная проверка».
  4. A proposed commit message: English, imperative, as in git log; no Co-Authored-By line.

Details are in the task file («Результат», «Ревью»). Do not commit — the user commits.

When the user says the task is committed: delete the task file and its line in work/backlog.md; a decision worth remembering goes into work/decisions.md (what, why, the date).

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

release

무료

Prepare a release of HoverTranslate — version, changelog, checks, live YouTube markup, store archives, and what the user uploads where. Uploads nothing itself.

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

kozii-d/hover-translate252026년 10월 23일 업데이트

task

무료

Research an idea for HoverTranslate and write it up as a task file in work/tasks/ for the implementer agent. Changes no code. An agent invokes it only after the user agreed to that very task in this conversation — propose it and ask first, never on its own judgement.

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

kozii-d/hover-translate252026년 10월 23일 업데이트

kozii-d의 스킬 모두 보기

이 스킬의 문제 신고