// Review recent edits and update all documentation including architecture docs, API specs, and edit history. Creates missing docs for new implementations.
Connect to Chrome via CDP proxy to automate web interactions — posting, scraping, form filling. Uses puppeteer-core (no bundled Chromium).
Short description — what this does and when to use it.
Orchestrate a multi-round implementation + review cycle. Use when coordinating a feature that requires implementation (FE/BE), design review (UIUX), security review, and QA verification. Ensures QA findings get routed back for fixes until clean.
Review recent edits and update all documentation including architecture docs, API specs, and edit history. Creates missing docs for new implementations.
Review code for best practices, modularity, scalability, abstraction, test coverage, redundancy, hardcoded values, type safety, performance, naming, API design, async patterns, config/env sync, template consistency, and documentation alignment. Generates detailed report with issues and recommendations.
| name | update-docs |
| description | Review recent edits and update all documentation including architecture docs, API specs, and edit history. Creates missing docs for new implementations. |
Review recent code changes and update ALL relevant documentation in the /docs folder.
Read today's edit history
docs/edit-history/ for the current date's session fileAnalyze changes
Update edit-history session file
Update CLAUDE.md if needed
Update PLAN.md (repo root) if needed
Update README.md (repo root) if needed
Update README.zh-CN.md (repo root) if README.md was updated
Update .env.example (repo root) if needed
.env.example.env.exampleUpdate docs/README.md if needed
Update docs/ files Review and update all architecture documentation to match current implementation
For each doc:
Create new docs if needed
Report summary