fix(skill): self-review — operator detection и continuation framing
- Зачем:
- Round 1 adversarial self-review нашёл 6 находок (3 high, 3 medium).
Артефакт первой итерации содержал противоречия между SKILL и README,
неточности про upstream-механики (Codex continuation, Agent Teams
gating SendMessage), и оставлял undefined load-bearing branch
"Operator available?". Без фиксов скилл вводил пользователей без
Agent Teams в ступор при Round 2.
- Что:
- SKILL Step 2: уточнено, что SendMessage gated на Agent Teams; Task
spawn без Agent Teams one-shot; Codex поддерживает intra-session
continuation.
- SKILL Step 4: "REQUIRED SUB-SKILL ... if available" заменено на
"Use ... when available" с явным fallback на inlined принципы.
- SKILL Step 6: добавлена continuation-support table по хостам,
восстановлена секция "Detecting an operator" с heuristic
(interactive если direct human message + user-facing channel).
- README: переписан Agent Teams блок под operator-gated модель; Codex
section — корректное описание intra-session continuation через /agent.
- EXPERIMENT.md: добавлен banner о предшествии редизайну и устаревших
ссылках на adversarial-reviewer.md.
- Проверка:
- Прогнать /claude-team-review в новой сессии с Agent Teams enabled
(env var добавлен в ~/.claude/settings.json) — Round 2 для проверки
continuation через SendMessage и operator-gating паттерна.
This commit is contained in:
@@ -62,8 +62,10 @@ the same host as the lead.
|
||||
```
|
||||
|
||||
The lead tries to **continue the same reviewer** for re-review when the
|
||||
host supports it (cheaper — context is preserved). When continuation is
|
||||
unavailable (Codex, or Claude Code without Agent Teams), or when the
|
||||
host supports it (cheaper — context is preserved). Codex supports
|
||||
intra-session continuation natively; Claude Code requires Agent Teams
|
||||
(`CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`) for the `SendMessage`-based
|
||||
continuation path. When continuation is unavailable, or when the
|
||||
previous reviewer is no longer reachable, the lead asks the operator
|
||||
before spawning a fresh subagent — full project re-read is expensive,
|
||||
and the operator may prefer to conclude the review unverified. Headless
|
||||
@@ -129,8 +131,9 @@ ln -s "$(pwd)" ~/.claude/skills/claude-team-review
|
||||
Claude Code watches `~/.claude/skills/` for changes and will pick the
|
||||
skill up without a restart.
|
||||
|
||||
**Optional — enable Agent Teams for cheaper re-review** (continuation
|
||||
between rounds instead of fresh-spawn). Add to your Claude Code settings:
|
||||
**Recommended — enable Agent Teams** for cheaper re-review. Continuation
|
||||
across rounds uses `SendMessage`, which is gated on Agent Teams. Add to
|
||||
your Claude Code settings:
|
||||
|
||||
```json
|
||||
{
|
||||
@@ -140,9 +143,11 @@ between rounds instead of fresh-spawn). Add to your Claude Code settings:
|
||||
}
|
||||
```
|
||||
|
||||
The skill works fine without Agent Teams — it falls back to a fresh
|
||||
subagent each round, with the previous-rounds context block packed into
|
||||
the briefing.
|
||||
Without Agent Teams, the Task-tool spawn is one-shot — every Round 2+
|
||||
re-review goes through the operator-gated fresh-spawn path (the operator
|
||||
decides between spawning a fresh subagent that re-reads the project, or
|
||||
concluding the review unverified). Headless runs without an operator
|
||||
conclude as `NOT VERIFIED`.
|
||||
|
||||
### Codex
|
||||
|
||||
@@ -155,11 +160,12 @@ mkdir -p ~/.codex/skills
|
||||
ln -s "$(pwd)" ~/.codex/skills/claude-team-review
|
||||
```
|
||||
|
||||
Codex spawns subagents without context continuation across spawns. The
|
||||
skill treats every re-review on Codex as an operator-gated decision —
|
||||
the lead asks whether to spawn a fresh subagent (full project re-read,
|
||||
expensive) or conclude without verification. Continuation can be added
|
||||
later if Codex grows that feature.
|
||||
Codex supports intra-session continuation natively — the lead can send
|
||||
follow-up instructions to a running subagent thread (use `/agent` to
|
||||
switch between active threads). The skill uses this for cheap re-review.
|
||||
When the previous subagent thread is no longer active, Round 2+ goes
|
||||
through the operator-gated fresh-spawn path (operator decides: spawn
|
||||
fresh with a full project re-read, or conclude unverified).
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
Reference in New Issue
Block a user