review
Collaborative code review using Agent Teams where reviewers discuss findings, challenge each other, and converge on a unified assessment. Evolves dm-work:review from isolated parallel reviewers to a review team.
What this skill does
# Team Review
Team-based collaborative code review using Agent Teams.
## Why teams > parallel subagents
Current /dm-work:review spawns 3 isolated subagents that report back independently. Findings may conflict, duplicate, or miss connections between concerns. With Agent Teams, reviewers can:
- Challenge each other ("I flagged this as security, but arch says the pattern is intentional")
- Cross-pollinate ("the perf issue I found is caused by the architecture pattern you identified")
- Converge on unified severity ratings instead of potentially conflicting ones
## When to use
- Complex PRs touching multiple domains
- Security-sensitive changes where arch context matters
- When previous reviews produced conflicting findings
- For straightforward reviews use `/dm-work:review` (subagent-based) — reach for the team variant only when reviewers genuinely benefit from challenging each other
## Team composition
| Role | Teammate | Model | Skills to inject |
|------|----------|-------|-----------------|
| Architecture | Teammate 1 | opus | dm-arch:solid-architecture, dm-arch:data-oriented-architecture |
| Code Quality | Teammate 2 | opus | Language-specific dm-lang:*-pro skill |
| Security | Teammate 3 | opus | (none — general security knowledge) |
| Lead | You | opus | Synthesis and final assessment |
Code reviewer may split by domain (same as dm-work:review) for large reviews.
## Scout phase
Still uses a haiku Explore subagent (not a teammate — too small for team overhead). Scout categorizes files, detects patterns, identifies hotspots, splits review domains.
## Review protocol
### Phase 1 — Scout (haiku subagent, same as dm-work:review)
- Categorize files, detect project type, identify hotspots
- Split into review domains with skill assignments
### Phase 2 — Independent review (teammates work in parallel)
- Each reviewer examines their domain
- Produces initial findings with severity and confidence
### Phase 3 — Cross-examination (teammates message each other)
- Reviewers share findings with the team
- Challenge findings they disagree with
- Identify connections between concerns
- Adjust severity based on cross-domain context
- 1-2 rounds of discussion
### Phase 4 — Unified assessment (lead synthesizes)
- Merge findings, resolve conflicts
- Apply severity filter (--min-severity)
- Deduplicate by file+line
- Produce final assessment
## Output format
Compatible with dm-work:review:
```markdown
## Review: <scope> (<N> commits, <LOC> across <M> files)
### Verdict: <emoji> <summary>
**Critical** (<count>)
1. `file:line` - <description> [Consensus: arch+security agreed]
**High** (<count>)
...
**Architecture**: <verdict + summary>
**Code Quality**: <verdict + summary>
**Security**: <verdict + summary>
### Review Discussion Notes
[Key debates between reviewers and resolutions]
```
New addition: "Review Discussion Notes" section captures inter-reviewer debates and resolutions — this is the unique value of team review over subagent review.
## Supports
- `--pr N` for PR mode (GitHub review comments)
- `--commits <range>` for explicit scope
- `--only <acs>` to filter reviewer types
- `--min-severity <level>` to filter output
- `--skip-beads` for local mode without bead creation
## Related
- **dm-work:review** — subagent alternative for straightforward reviews
- **dm-team:lead** — team coordination protocol
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.