本文へ移動
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 / 1000 文字

このフォームは 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 のスキルをすべて見る

このスキルの問題を報告する