review-method
/review-method
Unified review engine: the light review and the branch review (variants team-review and pr-review, and code-review), including signal-selected stack specialists. TRIGGER WHEN: the user asks to review current changes, a commit, a file, a plan, a specification, a document, a branch or a pull request for defects, or /daodan:review-changes, /daodan:review-branch or a lifecycle review phase runs a review. DO NOT TRIGGER WHEN: establishing the root cause of a reported failure without reviewing an artifact (use investigation-method), or removing dead code (use application-cleanup-method).
- Author
- acaprino ↗
- Repository
- daodan ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 7
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Unified review engine: the light review and the branch review (variants team-review and pr-review, and code-review), including signal-selected stack specialists. TRIGGER WHEN: the user asks to review current changes, a commit, a file, a plan, a specification, a document, a branch or a pull request for defects, or /daodan:review-changes, /daodan:review-branch or a lifecycle review phase runs a review. DO NOT TRIGGER WHEN: establishing the root cause of a reported failure without reviewing an artifact (use investigation-method), or removing dead code (use application-cleanup-method).
Original author description
Unified review engine: the light review and the branch review (variants team-review and pr-review, and code-review), including signal-selected stack specialists. TRIGGER WHEN: the user asks to review current changes, a commit, a file, a plan, a specification, a document, a branch or a pull request for defects, or /daodan:review-changes, /daodan:review-branch or a lifecycle review phase runs a review. DO NOT TRIGGER WHEN: establishing the root cause of a reported failure without reviewing an artifact (use investigation-method), or removing dead code (use application-cleanup-method).
How it works
SKILL.md has no level-two headings · 130 lines, 1,120 words
SKILL.md preview
--- name: review-method description: > Unified review engine: the light review and the branch review (variants team-review and pr-review, and code-review), including signal-selected stack specialists. TRIGGER WHEN: the user asks to review current changes, a commit, a file, a plan, a specification, a document, a branch or a pull request for defects, or /daodan:review-changes, /daodan:review-branch or a lifecycle review phase runs a review. DO NOT TRIGGER WHEN: establishing the root cause of a reported failure without reviewing an artifact (use investigation-method), or removing dead code (use application-cleanup-method). --- <daodan_host_binding host="opencode"> This binding governs execution of this package and its loaded references. It takes precedence over executable examples written for another host. Use only registered tools and their actual input schema; an example never creates a tool, argument, permission, model alias or nested worker capability. Preserve the generated worker allowlist, dependency closure, scope and delivery contracts. OpenCode V2 binding: repository reads use read/glob/grep, writes use write/edit/patch, shell execution uses shell, network tools are webfetch/websearch, and clarification uses the registered question tool. shell takes command, optional workdir, timeout in milliseconds and background. It does not provide interactive stdin. Persistent capture uses background: true and an explicit noninteractive stop signal. Load skills with skill using id: "<plugin>:<skill>". Dispatch registered roles with subagent using agent: "<owner>:<role>", description and prompt; optional sessionID continues that child, and background: true requests asynchronous completion. Use only roles allowed by the current harness and permissions. A child cannot dispatch nested workers when its permissions or the configured depth deny it. Workflow entries are /<plugin>:<workflow>, registered by the package loader. Inherit the session model; an override requires its authorized, actually available provider/model identity, not another host's short model alias. The loader includes required local providers and registers plugin-declared MCP servers. Qualified foreign providers need a compatible V2 plugin/skill provisioned through this host, never a Claude marketplace command. Check the active registry: registration metadata alone does not prove a connected server or usable tool. Inherit the active session's model and default variant. A source model alias such as sonnet is not a portable override; request a different model only through an explicit adapter mapping to a valid host identity and user authorization. The executing agent and its coordinator own continuation, recovery, verification and delivery. Skills supply knowledge and method instructions; they are not executors or a runtime persistence mechanism. Resolve each component by kind and exact installed identity. A role is dispatched as a worker, a skill loads instructions, and a workflow starts its declared method. Kernel owner-qualified skill references are logical provider identities: resolve them to the actual host registry name and verified installed provider path. Do not invent a registry string by adding an owner's prefix when the host does not use it. Do not load an agent identity as a skill or execute a workflow name as a shell command. Declared required foreign providers remain mandatory. If a required provider or capability (including required MCP access or isolation) is unavailable, stop its dependent phase and report the missing capability. Optional external providers follow the method's declared selection and absence behavior; their absence alone does not block the base workflow. Report any explicitly requested but unavailable provider contribution as unfulfilled and continue independent work. Do not install a different host's plugin or substitute unrelated skills to claim coverage. Shell execution alone does not establish interactive stdin. Before a capture or checkpoint, use an available session-control mechanism. When stdin is unavailable, keep user-driven capture in a supported background process with bounded output and an explicit stop signal controlled by the coordinator after the user's completion message. Close owned browser/process resources on completion or cancellation. Continue working within the current authorization while the requested result is achievable. After a tool error, inspect its cause, correct the relevant input or implementation, retry when justified and verify the outcome; never repeat a failing action blindly. Do not close the turn with a promise or a partial result when an authorized next step can still produce or verify the requested result. Stop only for a documented real impediment, a missing required capability, an unresolved human decision or the caller's stop request. At that boundary, report completed results, remaining work and the concrete prerequisite for continuation; continue any independent work that the blocker does not prevent. A tool's successful exit, a worker stop or an idle session is not the deliverable. Return final text naming observed findings, artifact paths, executed checks and blockers. An empty worker result is missing delivery: inspect or resume that worker when permitted, or record failure. Verify required artifacts and candidate gates before marking the requested outcome complete. This is an execution binding, not a rewrite of source examples. Preserve programming language fences, domain code and host APIs that are the subject of marketplace-ops or agent-sdk-builder. A host-as-subject API is not a tool provided to this session. Compiled binding and static checks do not prove an installed host executed a run. </daodan_host_binding> # Unified review method Input: variant, target/flags, output root; optional same-snapshot `prepared` bundle. Preparation resolves absent `shape` (`light`/`branch`) and `target-kind` (`changeset`/`plan`/`spec`/`doc`). Output: native report and project-result envelope. **Shape `light`:** read only `references/light.md` in this method. Branch uses `team-review`, or `pr-review` for a pull request, through these steps. Do not delegate execution to another workflow or nested lifecycle scheduler. For team-review Phase 1a, the coordinator executes `codebase-map:map-method` analyze preflight, answerable checkpoints, delivery check and publication decision. Its `codebase-map:map-analyst` executes requested phases in one isolated context through the declared host harness. Loading a method executes no phase; the analyst is a role, never a skill or declarative `invoke`. Keep one review preparation and final report owner; required workers retain isolation. The workflow sidecar declares `dispatch.roles` and isolated inline workers. Inline lens, critic, history, hygiene and minimal-fix briefs use `work-controller:isolated-worker` through that host binding, never an invented generic role. Bind scope, authorization, budget, report path and delivered/failed outcome for every brief. 1. Load `senior-review:review-preparation`, unless a prepared bundle exists. Validate target, run, snapshot, knowledge schema/candidate/fingerprints/scope, delivery IDs and applicable activation evidence or skip/gap reason. Reprepare stale or incomplete bindings against this candidate, without another run or duplicate dispatch. 2. Read `references/<variant>.md`. Dispatch validated `jobs` once each under preparation's `references/composition.md`, including stack members. The roster supplies coverage obligations, never another dispatch list. Core inputs remain canonical in `senior-review:review-quality-gates`; stack members use their provider definitions and shared preparation. Preserve `knowledge_selection`; assign scoped `knowledge_ids`, fingerprint and exact catalog load/reference bindings. Workers read assigned knowledge, apply it against source and return `knowledge_usage` with scope, worker, hashes, references and application evidence. Account for knowledge lenses in the same ledger. No worker receives peer findings before delivery. Use isolated contexts and the host's coordination mechanism. Account for every selected worker before starting consolidation. Each member retains canonical checks, coverage and finding references. Context, blind derivation and verification keep separate inputs and deliveries. 3. Load `senior-review:review-consolidation` with native results. Finish it before the variant's output/fix tail. 4. Code review then reads `references/code-review-delivery.md`; team/PR delivery stays in consolidation. Execute delivery and authorized fixes once. Application subtraction uses `senior-review:application-cleanup-method`; significant semantic refactors return to the caller's development plan, never cleanup. Read-only review preserves application files and preexisting edits. Before accepted fixes load `work-controller:work-record` for preflight, authorizations, baseline, candidate gate and owned recovery. Commit/publication require separate authorization; review grants neither.
Files in this package (7)
- SKILL.md 9 KB
- SKILL.toml 1 KB
- references/code-review-delivery.md 8 KB
- references/code-review.md 10 KB
- references/light.md 9 KB
- references/pr-review.md 7 KB
- references/team-review.md 18 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · acaprino/daodan | 96 | MIT |
| acaprino/alfio-claude-plugins | 96 | MIT |
| acaprino/daodan | 96 | MIT |
| acaprino/alfio-claude-plugins | 96 | MIT |
| acaprino/alfio-claude-plugins | 96 | MIT |
| acaprino/alfio-claude-plugins | 96 | MIT |
| acaprino/daodan | 96 | MIT |
| acaprino/alfio-claude-plugins | 96 | MIT |
| acaprino/daodan | 96 | MIT |
Database snapshot: 13.11.2026 · package version 083669fefd31 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 96code-review
Use when the user asks for a code review of a change, branch or PR. - 100pr-review
Bug-first, evidence-only review of a pull request or branch-versus-base diff. Use when the user explicitly asks to review a pull request, supplies a PR number or URL, names a branch comparison, or asks to review changes since a fixed point. - 100create-pull-request
Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository. - 90branch-pr
Prepare branch state and open pull requests with consistent review metadata. Trigger: when a user asks to create a PR, prepare a branch for review, or check PR readiness. - 100code-review
This skill should be used when the user asks for a code review of a change — a pull request, merge request, branch, commit range, working-tree change, or pasted diff — covering correctness, security, performance, structure, and repository-specific rules. Trigger on phrases like… - 100abstraction-architect
Structural entropy knowledge base: canonical ownership, duplicated domain rules, redundant models and abstraction fitness. TRIGGER WHEN: deciding whether to extract, centralize or inline; asking who owns a rule or state; auditing duplicated knowledge or competing sources of…