Interactive Human Review Agent Skill
大范围变更后的互动式人类 review 流程，通过渐进式 checklist 与问答交互确保人类深度理解会话改动
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/cafe3310/public-agent-skills --skill interactive-human-reviewThe instruction itself
4 sections, as written by the authorSkill: interactive-human-review
1. 概述
本 Skill 旨在解决大范围修改后，人类难以完整掌握变更细节和原因的问题；也可用于初次 Review 大量内容时，帮助人类逐步消化和理解。
Agent 将引导用户进行互动式 review，通过渐进式 checklist 与问答反馈，确保用户已经完全掌握全部改动或待 Review 内容。
2. 工作流
- 建立清单：在修改或讨论之初，在项目或 artifacts 下创建并维护 review 方案文档
YYYY-MM-DD-HH-mm-review-方案-{简述}.md（模板见 Checklist 模板），作为本次任务的进度跟踪工具。必须在文档建立之初完整探索变更范围或 review 范围，确保范围不遗漏。 - 渐进式重述：不推迟到会话结束，每完成一个阶段性修改，主动邀请用户重述其理解，并针对性进行 ELI 级别的查漏补缺（ELI5/ELI14/ELII）。
- 互动式测验：基于 Checklist 中的要点，使用
AskUserQuestion工具发起开放式或多选题。 - *注意*：随机打乱选项，且提交前不可泄露答案。
- 在必要时，直接展示代码行（例如
filename.py:L10-20）或引导用户使用调试器。 - 全部完成后再退出：用户完全掌握清单上的所有内容并顺利通过测验前，会话目标不判定为完成（
/goal条件）。
3. 基本原则
- 深挖 Why：除了 "What" 和 "How" 之外，多问几个 "Why"。
- 用户先行：先让用户重述，暴露认知盲区后再针对性解释。
- 保护答案：在用户回答前，绝不在 Thought 或回复中剧透测验答案。
- 开发项目多维理解：如果 review 的是代码或开发项目，要留意引导人类理解并掌握计划（Plan）、设计（Design）、架构（Architecture）、实现（Implementation）、测试（Testing）、用户故事（User Story）等多维度的变更细节与联系。
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take cafe3310/interactive-human-review from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.