review
The review skill opens an interactive web interface where users can evaluate and provide feedback on content through checkboxes and comments. Use it when users request review of plans, documents, code, or other content by saying "review this," "check this plan," or providing a file path, enabling structured approval or rejection with optional notes before processing results.
git clone --depth 1 https://github.com/team-attention/plugins-for-claude-natives /tmp/review && cp -r /tmp/review/plugins/interactive-review/skills/review ~/.claude/skills/reviewSKILL.md
# Interactive Review Skill
This skill opens an interactive web UI where users can review content with checkboxes and comments.
## How It Works
1. Determine the content source:
- **If user specifies a file path**: Use the `Read` tool to get the file contents
- **If user provides content directly**: Use that content as-is
- **Otherwise**: Collect the most recent relevant content from the conversation
2. Call `mcp__interactive_review__start_review` with the content
3. A browser window opens automatically with the review UI
4. User reviews each item:
- Check/uncheck to approve/reject
- Add optional comments
5. User clicks Submit
6. Process the feedback and respond accordingly
## Content Sources (Priority Order)
1. **Explicit file path**: User says "review /path/to/file.md" or "이 파일 리뷰해줘: README.md"
- Read the file using `Read` tool and use its contents
2. **Direct content**: User provides or references specific content to review
- Use the provided content directly
3. **Conversation context**: Extract relevant content from recent conversation
- Plans, documents, code, etc. that were recently discussed
## Usage
When the user wants to review content:
```
# If file path is specified, read it first:
Read({ "file_path": "/path/to/file.md" })
# Then start the review:
mcp__interactive_review__start_review({
"content": "<content from file or conversation>",
"title": "<descriptive title>"
})
```
## Processing Results
The tool returns a JSON with review items. Handle each item based on:
| checked | comment | Action |
|---------|---------|--------|
| true | empty | Approved - proceed as planned |
| true | has text | Approved with note - consider the feedback |
| false | has text | Rejected - modify according to comment |
| false | empty | Rejected - remove or reconsider this item |
## Example Flow
User: "Review this implementation plan"
1. Extract the plan content from recent output
2. Call start_review with the content
3. Wait for user feedback (tool blocks until submit)
4. Present summary of feedback
5. Ask if user wants you to proceed with approved items or revise rejected items
## Response Template
After receiving feedback:
```
## Review Summary
**Approved**: X items
**Needs revision**: Y items
### Items requiring changes:
- [Item]: [User's comment]
Would you like me to:
1. Proceed with approved items
2. Revise the rejected items based on feedback
3. Both - revise then proceed
```Collect and synthesize opinions from multiple AI agents. Use when users say "summon the council", "ask other AIs", or want multiple AI perspectives on a question.
This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium). Trigger on "내용 vs 형식", "content vs form", "metamedium", "형식을 바꿔볼까", "새로운 포맷", "관점 전환", "perspective shift", "다른 방법 없을까", "같은 방식이 안 먹혀", "diminishing returns". Applies Alan Kay's metamedium concept to surface form-level alternatives. For requirement clarification use vague; for strategy blind spots use unknown.
This skill should be used when the user provides a strategy, plan, or decision document and wants to surface hidden assumptions and blind spots using the Known/Unknown 4-quadrant framework. Trigger on "known unknown", "4분면 분석", "blind spots", "뭘 놓치고 있지", "뭘 모르는지 모르겠어", "전략 점검", "전략 분석", "assumption check", "가정 점검", "quadrant analysis", "what am I missing". Strategy-level blind spot analysis with hypothesis-driven questioning. For requirement clarification use vague; for content-vs-form reframing use metamedium.
This skill should be used when the user's request or requirement is ambiguous and needs iterative questioning to become actionable. Trigger on "clarify requirements", "refine requirements", "요구사항 명확히", "요구사항 정리", "뭘 원하는 건지", "make this clearer", "spec this out", "scope this", "/clarify". Turns vague inputs into concrete specs. For strategy blind spots use unknown; for content-vs-form reframing use metamedium.
개발 커뮤니티에서 기술 주제에 대한 다양한 의견 수집. "개발자 반응", "커뮤니티 의견", "developer reactions" 요청에 사용. Reddit, HN, Dev.to, Lobsters 등 종합.
This skill should be used when the user asks to "기술 의사결정", "뭐 쓸지 고민", "A vs B", "비교 분석", "라이브러리 선택", "아키텍처 결정", "어떤 걸 써야 할지", "트레이드오프", "기술 선택", "구현 방식 고민", or needs deep analysis for technical decisions. Provides systematic multi-source research and synthesized recommendations.
This skill should be used when the user asks to "트윗 가져와", "트윗 번역", "X 게시글 읽어줘", "tweet fetch", "트윗 내용", "트윗 원문", or provides an X/Twitter URL (x.com, twitter.com) and wants to read, translate, or analyze the tweet content. Also useful when other skills need to fetch tweet text programmatically.
This skill should be used when the user asks to "check email", "read emails", "send email", "reply to email", "search inbox", or manages Gmail. Supports multi-account Gmail integration for reading, searching, sending, and label management.