From wize-doc
Revise existing feature documentation using a change description and optional new context (code analysis, Linear, Notion). Preserves unchanged sections verbatim. Used internally by the /document command update flow.
npx claudepluginhub goworkwize/wize-docThis skill uses the workspace's default tool permissions.
Revise an existing feature documentation file based on what changed.
Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.
Executes ctx7 CLI to fetch up-to-date library documentation, manage AI coding skills (install/search/generate/remove/suggest), and configure Context7 MCP. Useful for current API refs, skill handling, or agent setup.
Share bugs, ideas, or general feedback.
Revise an existing feature documentation file based on what changed.
From the command:
Read the existing doc in full. Identify the sections present (headings and their content).
Based on the user's change description and any new context provided, identify which sections need updating:
Sections not touched by the change should be preserved verbatim.
For each affected section:
If critical information is missing or the change description is ambiguous, ask the user before rewriting.
Write the complete updated document back to the same file path (overwrite).
Keep all unaffected sections exactly as they were.
Report back:
If the doc's Related Resources section references a Notion page, offer once:
"Doc updated at
<path>. Want me to also update the Notion page?"
Only proceed if the user confirms. Use notion-update-page with the existing page ID.