review-notes

Automating technical documentation generation is handled by extracting code context to create structured documents covering core technology, code snippets, call chains, and architecture overviews. This Skill triggers automatically when discussing architecture or design within coding tools like Cursor or Claude Code.

Generating technical docs in WPS Notes integrates with coding assistants by triggering automatically during code discussions. When you mention terms like "architecture diagram" in comments or prompts, it creates or updates a WPS Note with detailed technical documentation, core code snippets, and relevant diagrams.

Creating a technical document for code review includes structured sections for core technology, code snippets, key points, class responsibilities, call chains, architecture overviews, and notes. This ensures all critical architectural and logic details are documented and accessible within WPS Notes.

Yes, you need the WPS Note API to generate and update technical docs automatically. The API is required for reading, writing, and image generation capabilities within WPS Notes, enabling the automated creation of structured technical documents and architecture diagrams.

Yes, you can use this automated documentation tool with Cursor, Codex, and Claude Code. It works seamlessly with these coding tools by triggering automatically from user prompts and comments when discussing architecture, design, or core methods.

The best way to keep technical documentation updated while coding is through contextual integration with coding tools. This Skill automatically generates or updates WPS Notes documents based on real-time code context, ensuring architecture and core logic details remain synchronized with the codebase.