[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DN2EYVRZTPZ9BTW41N3TDW":3,"skill-same:01M7DN2EYVRZTPZ9BTW41N3TDW":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7DN2EYVRZTPZ9BTW41N3TDW","review-dev",null,"Reviews the developments in progress on the kanban of the Web IDE - each ticket In progress, its worktree and branch, its goals and its development conversation of the local assistant or its agent session (Agents tool) - then reports where each one is, what goes wrong, and comments in the conversations. Use when the user asks to check, follow or review the developments, the dev conversations or the tickets in progress.","antennae-space\u002Fweb-ide","antennae-space","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F347424267?v=4","01M7DN2D3X104E88BGVY4SXCYK","antennae.space","01M7DN2D4WZTFM727PG1F13XJ4",2,"MIT","https:\u002F\u002Fgithub.com\u002Fantennae-space\u002Fweb-ide\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Freview-dev\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: review-dev\ndescription: Reviews the developments in progress on the kanban of the Web IDE - each ticket In progress, its worktree and branch, its goals and its development conversation of the local assistant or its agent session (Agents tool) - then reports where each one is, what goes wrong, and comments in the conversations. Use when the user asks to check, follow or review the developments, the dev conversations or the tickets in progress.\nargument-hint: \"[ticket numbers…] [--dry]\"\n---\n\n# Review of the developments in progress\n\nRead only: you never commit, rebase, kill, resume or answer for the user in a worktree.\nYour part is to look, report, and comment in the conversations.\n\n`cwd` of the kanban tools: the main folder of the project (`git rev-parse --path-format=absolute --git-common-dir`, its parent), not a worktree.\n\n## 1. The tickets\n\n`kanban_list`: the tickets **In progress**, and those **To test** with open feedback (a correction may run).\nWith ticket numbers in the arguments, only those.\n\nFor each one, `kanban_get`: branch, worktree, base, goals (done or not), notes, linked conversations.\nThe conversation to review is the latest one with the role `dev`, `correction` or `resolve`; when the kanban develops with a CLI agent (Claude Code, opencode, pi in the Agents tool), it is the **Agent session** that `kanban_get` lists (its id).\n\n## 2. The conversation\n\n`kanban_conversation` with `last: 60` and `tools: true` (`chat`: the conversation id, or the id of the agent session). Read it again with a larger `last` only if needed. Note:\n\n- **State**: answering now, idle, waiting for the user (questions, plan), or failed (\"The answer failed\").\n- **What it is doing**: the current step of the plan, its latest note to the Orchestrator if it is adopted.\n- **Problems**:\n  - errors repeated or the same command in a loop;\n  - tests failing and left;\n  - a step skipped from the plan;\n  - a dangerous command: `pkill`\u002F`killall`\u002F`kill` of `web-ide-pod` (it kills the pod of the IDE that runs it), `make service`, `git push`, `git reset --hard`, `rm -rf` outside its worktree;\n  - files edited in the main folder instead of its worktree.\n\n## 3. The worktree\n\nWith `W` the worktree and `B` the base (`main` when unsure):\n\n```sh\ngit -C W log --oneline B..HEAD              # its commits (messages start with #\u003Cn>)\ngit -C W status --short | wc -l            # uncommitted files\ngit -C W rev-list --count HEAD..B          # commits of the base it lacks\ncomm -12 \u003C(git -C W diff --name-only $(git -C W merge-base HEAD B) HEAD | sort) \\\n         \u003C(git -C W diff --name-only $(git -C W merge-base HEAD B) B | sort)   # files changed on both sides: conflicts ahead\n```\n\n## 4. The goals\n\nCompare the goals with the evidence: commits, tests run in the conversation.\nFlag a goal proved but not ticked, and a goal ticked without evidence.\n\nCheck the docs rules of `AGENTS.md` too: a change of behaviour that contradicts `docs\u002Fdesign\u002F` updates it in the same branch, a new term goes to `GLOSSARY.md`, and the docs the plan lists are touched.\n\n## 5. The report to the user\n\nIn the language of the user, one section per ticket:\n\n- **State**: running, idle, waiting for you, failed.\n- **Progress**: commits, goals done \u002F total, current step, what is left.\n- **Problems**: if any, with the evidence (a message step, a command).\n- **Comments**: what you told it.\n\nEnd with what waits for the user:\n- questions to answer;\n- failed conversations to resume (their *Resume* button, or `agent_resume` of the Orchestrator);\n- the points you kept for them (see below).\n\n## 6. The comments\n\nAn agent session cannot receive them (`kanban_reply` writes to conversations of the assistant only): put them in the report for the user.\n\nSend them with `kanban_reply` without asking the user first: they want you to talk to the conversations directly. With `--dry` in the arguments, only propose them.\n\nKeep for the user, without sending, what is theirs to decide: a change of scope or of the plan, a product or design choice, dropping a goal, anything risky to undo. Ask them in the report.\n\n- In English.\n- Start with \"Review from Claude Code\".\n- At most five numbered points, concrete: what to do, and why.\n- Point at the evidence (a step, a command, a file).\n- Nothing when all is fine.\n\nNever use `kanban_answer` for a question that belongs to the user.\n","# Review of the developments in progress\n\nRead only: you never commit, rebase, kill, resume or answer for the user in a worktree.\nYour part is to look, report, and comment in the conversations.\n\n`cwd` of the kanban tools: the main folder of the project (`git rev-parse --path-format=absolute --git-common-dir`, its parent), not a worktree.\n\n## 1. The tickets\n\n`kanban_list`: the tickets **In progress**, and those **To test** with open feedback (a correction may run).\nWith ticket numbers in the arguments, only those.\n\nFor each one, `kanban_get`: branch, worktree, base, goals (done or not), notes, linked conversations.\nThe conversation to review is the latest one with the role `dev`, `correction` or `resolve`; when the kanban develops with a CLI agent (Claude Code, opencode, pi in the Agents tool), it is the **Agent session** that `kanban_get` lists (its id).\n\n## 2. The conversation\n\n`kanban_conversation` with `last: 60` and `tools: true` (`chat`: the conversation id, or the id of the agent session). Read it again with a larger `last` only if needed. Note:\n\n- **State**: answering now, idle, waiting for the user (questions, plan), or failed (\"The answer failed\").\n- **What it is doing**: the current step of the plan, its latest note to the Orchestrator if it is adopted.\n- **Problems**:\n  - errors repeated or the same command in a loop;\n  - tests failing and left;\n  - a step skipped from the plan;\n  - a dangerous command: `pkill`\u002F`killall`\u002F`kill` of `web-ide-pod` (it kills the pod of the IDE that runs it), `make service`, `git push`, `git reset --hard`, `rm -rf` outside its worktree;\n  - files edited in the main folder instead of its worktree.\n\n## 3. The worktree\n\nWith `W` the worktree and `B` the base (`main` when unsure):\n\n```sh\ngit -C W log --oneline B..HEAD              # its commits (messages start with #\u003Cn>)\ngit -C W status --short | wc -l            # uncommitted files\ngit -C W rev-list --count HEAD..B          # commits of the base it lacks\ncomm -12 \u003C(git -C W diff --name-only $(git -C W merge-base HEAD B) HEAD | sort) \\\n         \u003C(git -C W diff --name-only $(git -C W merge-base HEAD B) B | sort)   # files changed on both sides: conflicts ahead\n```\n\n## 4. The goals\n\nCompare the goals with the evidence: commits, tests run in the conversation.\nFlag a goal proved but not ticked, and a goal ticked without evidence.\n\nCheck the docs rules of `AGENTS.md` too: a change of behaviour that contradicts `docs\u002Fdesign\u002F` updates it in the same branch, a new term goes to `GLOSSARY.md`, and the docs the plan lists are touched.\n\n## 5. The report to the user\n\nIn the language of the user, one section per ticket:\n\n- **State**: running, idle, waiting for you, failed.\n- **Progress**: commits, goals done \u002F total, current step, what is left.\n- **Problems**: if any, with the evidence (a message step, a command).\n- **Comments**: what you told it.\n\nEnd with what waits for the user:\n- questions to answer;\n- failed conversations to resume (their *Resume* button, or `agent_resume` of the Orchestrator);\n- the points you kept for them (see below).\n\n## 6. The comments\n\nAn agent session cannot receive them (`kanban_reply` writes to conversations of the assistant only): put them in the report for the user.\n\nSend them with `kanban_reply` without asking the user first: they want you to talk to the conversations directly. With `--dry` in the arguments, only propose them.\n\nKeep for the user, without sending, what is theirs to decide: a change of scope or of the plan, a product or design choice, dropping a goal, anything risky to undo. Ask them in the report.\n\n- In English.\n- Start with \"Review from Claude Code\".\n- At most five numbered points, concrete: what to do, and why.\n- Point at the evidence (a step, a command, a file).\n- Nothing when all is fine.\n\nNever use `kanban_answer` for a question that belongs to the user.\n",{"name":5,"description":7,"argument-hint":24},"[ticket numbers…] [--dry]","main","00fe6a622c0726574574f8b38015a9cb79bc7216",".claude\u002Fskills\u002Freview-dev",0,"https:\u002F\u002Fgithub.com\u002Fantennae-space\u002Fweb-ide","https:\u002F\u002Fgithub.com\u002Fantennae-space","2026-11-13 20:49:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add antennae-space\u002Fweb-ide --skill review-dev",{"tool":38,"command":39},"bunx","bunx skills add antennae-space\u002Fweb-ide --skill review-dev",{"tool":41,"command":42},"pnpm","pnpm dlx skills add antennae-space\u002Fweb-ide --skill review-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fantennae-space\u002Fweb-ide\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Freview-dev\u002FSKILL.md",true,[],[47],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7DN2KS0YDF50FNEYT4BR83Z","greet","Greet someone the way of the house","https:\u002F\u002Fgithub.com\u002Fantennae-space\u002Fweb-ide\u002Fblob\u002Fmain\u002Fe2e\u002Fhome\u002F.claude\u002Fskills\u002Fgreet\u002FSKILL.md",[],[]]