consensus-review
Runs independent multi-model reviews of a requested diff, verifies findings and merges duplicates. Use when the user explicitly asks for multiple independent opinions rather than a normal single review.
- License 许可
- GPL-3.0
- 所属仓库
- Artawower/kaizen
- 最近更新
- 2026-11-10
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- consensus-review
- description
- Runs independent multi-model reviews of a requested diff, verifies findings and merges duplicates. Use when the user explicitly asks for multiple independent opinions rather than a normal single review.
03 SKILL.md 正文
Consensus Review
Use ../../references/code-reviewer.md as the shared review policy.
Scope and reviewers
Determine the exact requested diff. In Jujutsu repositories, use jj diff or the
requested revision range. Do not substitute a Git working-copy diff for a jj revision.
Stop if the requested diff is empty.
Discover available authenticated models and delegation tools instead of assuming that an MCP bridge or a particular model version exists. Choose two or three independent reviewers, preferably across model families, using exact available provider/model IDs. Respect the active orchestration policy.
If fewer than two reviewers are available, disclose that limitation rather than claiming consensus. Do not install providers or change credentials for the review.
Workflow
- Send the same task, acceptance criteria and diff scope to each reviewer independently.
- Collect their results without showing one review to the other reviewers.
- Verify proposed findings against the actual code.
- Merge duplicates and reject unsupported claims or stylistic preferences.
- Return the models used, confirmed issues, material disagreements and verification gaps.
Respond in the user's language. Create persistent report files only when requested, using names derived from the models actually used rather than historical version labels.
04 同仓库更多 Skills
yt-analyze
Fetch YouTrack task + comments via MCP, critically analyze relevance and requirements, produce concise summary of what to implement, and build an implementation plan mapped to codebase. Trigger - YouTrack issue ID or request to "analyze task", "plan task", "break down YT issue".
youtrack-task
Analyzes a YouTrack issue, reviews comments and attachments, and proposes or creates actionable subtasks. Use when the user gives a YouTrack issue ID and wants synthesis, decomposition, or follow-up tasks.
youtrack-search
Searches YouTrack from natural language or native query syntax and returns a concise report with the most relevant issues. Use when the user wants to find issues, triage work, or translate a plain-language query into YouTrack search.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
vitest
Plan and write Vitest tests for changed code. Analyses git diff, checks existing tests, produces a concrete test plan using flat test structure (no describe/it blocks). Use when adding tests for new/changed code, improving Vitest coverage, or asking what to test after a change.