review-with-docs

Reviews code changes for quality, documentation sync, and AI-generated dead code.

5|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/A158Coke/WotbTools --skill review-with-docs-a158coke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-with-docs
Source: https://github.com/A158Coke/WotbTools/tree/main/.agents/skills/review-with-docs
Command: npx skills add https://github.com/A158Coke/WotbTools --skill review-with-docs-a158coke

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @alibaba-group/open-code-review.

What problem does it solve? After code changes are made, teams often ship inconsistent documentation, unmet plan requirements, and speculative dead code left behind by AI assistants. This Skill runs a structured three-layer audit that catches requirement gaps, code defects, and documentation drift before merge. ## Core Features & Use Cases - Three-layer review engine: Layer A audits plan/requirement compliance, DI injection patterns, and documentation sync; Layer B uses Alibaba OpenCodeReview (OCR) delegate mode for deterministic diff scoping and rule-based file review; Layer C reconciles, deduplicates, and re-rates findings into BLOCKER/MAJOR/MINOR severities. - Documentation synchronization checklist: Verifies CHANGELOG, DEVELOPER_GUIDE, README, API docs, i18n locales (zh/en/ru), code comments, config annotations, plan files, and frontend versions.json stay consistent with the change. - AI dead code cleanup: Detects and removes speculative abstractions, single-implementation interfaces, never-populated fields, and unreferenced methods with repo-wide zero-reference scans and safe-deletion boundaries. - Use Case: After finishing a feature branch that touches the API, frontend, and export columns, run this Skill to confirm every plan requirement is implemented, review the diff against OCR rules, fix blockers, and verify all docs and locale files were updated before opening a PR. ## Quick Start Ask the agent to run the review-with-docs skill on the current branch changes to audit plan compliance, code quality, dead code, and documentation synchronization.

Frequently Asked Questions about review-with-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code changes and documentation together before merging?

Run this Skill after completing code changes. It audits plan compliance, reviews the diff via OpenCodeReview delegate mode, checks documentation sync across CHANGELOG, README, API docs, and i18n files, then outputs a blocker count that must reach zero before merge.

What is OpenCodeReview delegate mode used for in code review?

Delegate mode uses the OCR CLI for deterministic work only: computing merge-base diff scope, filtering reviewable files, and grouping review rules. The actual reasoning is done by the main agent, so no separate LLM API key or OCR-side model configuration is needed.

How do I detect and remove AI-generated dead code safely?

The Skill scans for single-implementation abstractions, never-populated fields, and unreferenced methods, then proves zero references with repo-wide searches including tests, scripts, and locales. It classifies findings as truly dead, falsely dead, or uncertain, and only deletes safe cases.

Does this review process work when the OCR CLI is unavailable?

Yes, but tool failure is never treated as no findings. The plan audit continues regardless, and the reviewer must either manually cover the diff using the standard checklist or explicitly mark the review as incomplete rather than reporting zero blockers.

What are the limitations of diff-based code review for plan compliance?

Diff review cannot detect missing implementations because unwritten code produces no diff. That is why the Skill separates Layer A plan auditing from Layer B diff review, treating any unmet requirement as a blocker even when the diff review reports no findings.