From d7bee9bdf200c1700fa1cdb1d435cc45a51f9a50 Mon Sep 17 00:00:00 2001 From: catlog22 Date: Thu, 20 Nov 2025 15:48:06 +0800 Subject: [PATCH] docs: clarify path parameter description in /memory:docs command MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Improve the path parameter documentation to eliminate ambiguity: - Change "Target directory" to "Source directory to analyze" - Explicitly state documentation is generated in .workflow/docs/{project_name}/ at workspace root - Emphasize docs are NOT created within the source path itself - Add concrete example showing path mirroring behavior This resolves potential confusion about where documentation files are created. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .claude/commands/memory/docs.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.claude/commands/memory/docs.md b/.claude/commands/memory/docs.md index 52416c9a..76f0142c 100644 --- a/.claude/commands/memory/docs.md +++ b/.claude/commands/memory/docs.md @@ -44,7 +44,11 @@ Lightweight planner that analyzes project structure, decomposes documentation wo /memory:docs [path] [--tool ] [--mode ] [--cli-execute] ``` -- **path**: Target directory (default: current directory) +- **path**: Source directory to analyze (default: current directory) + - Specifies the source code directory to be documented + - Documentation is generated in a separate `.workflow/docs/{project_name}/` directory at the workspace root, **not** within the source `path` itself + - The source path's structure is mirrored within the project-specific documentation folder + - Example: analyzing `src/modules` produces documentation at `.workflow/docs/{project_name}/src/modules/` - **--mode**: Documentation generation mode (default: full) - `full`: Complete documentation (modules + README + ARCHITECTURE + EXAMPLES + HTTP API) - `partial`: Module documentation only (API.md + README.md)