total-review
Run Fable and GPT reviews, then combine their findings for the user's approval. Use only when the user explicitly invokes /total-review.
- License 许可
- MIT
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- total-review
- source
- https://github.com/davidondrej/skills
- license
- MIT
- description
- Run Fable and GPT reviews, then combine their findings for the user's approval. Use only when the user explicitly invokes /total-review.
- imported_at
- 2026-09-20
- source_path
- skills/agent-orchestration/total-review/SKILL.md
- source_repository
- davidondrej/skills
- disable-model-invocation
- true
03 SKILL.md 正文
Total Review
Workflow
-
Launch both reviewers in parallel as two bb threads (default). Follow
/nagent,/bb-cli, and each reviewer skill:- One
fable-reviewworker (Fable 5 Max 1M). - One
gpt-reviewworker (GPT 5.6 Sol Max). - Follow each reviewer skill exactly: neutral prompt, broad review scope, detailed findings on critical/serious issues, concise plain-English final report.
- Reuse this thread's environment so both see the same files.
- If the user names another harness (Cursor Task, cmux, Codex CLI, etc.), use that for both instead.
- One
-
Wait for both to finish (
bb thread waiton each, unless another harness was requested). Do not start triage until both reports are back. -
Merge and triage. Read both reports in full. Then:
- Combine and deduplicate findings; an issue reported by both counts once.
- Assess each finding: is it a real bug or risk, or a style preference, theoretical edge case, or non-issue? Agreement alone does not prove an issue is real.
- Keep only issues that matter.
-
Output to the user — clear and very concise:
- A numbered list of real issues, one line each: what it is + where.
- Mark which reviewer(s) found each:
[both],[fable], or[gpt]. Issues found by both go first. - One short line at the end: how many findings were dropped as overthinking.
- Then ask the user: approve fixing these, or adjust the list.
-
On approval, fix and ship. Fix only approved issues. Then stage, commit with a clear message, and push to GitHub using the standard ship workflow.
Rules
- Keep every step's output short and in plain English.
- Show the merged shortlist by default; provide full reviewer reports only if the user asks.
- Never fix an issue before the user approves the shortlist.
04 同仓库更多 Skills
dei-assessment
Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.
dei-action-plan
Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.
culture-fit-assessment
Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.
cowork-to-code-bridge
Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.
counter-offer-response
Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.
continuous-feedback-system
Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.