@iamdangavin/claude-skill-vitepress-docs 1.0.0 → 1.4.0

package/README.md

@@ -0,0 +1,2 @@
+# claude-skill-vitepress-docs
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iamdangavin/claude-skill-vitepress-docs",
-  "version": "1.0.0",
+  "version": "1.4.0",
   "description": "Installs the vitepress:docs Claude Code skill — VitePress docs setup, generation, screenshots, and sync.",
   "type": "module",
   "bin": {
@@ -17,5 +17,8 @@
     "vitepress",
     "docs"
   ],
-  "license": "MIT"
+  "license": "MIT",
+  "publishConfig": {
+    "access": "public"
+  }
 }

package/skill/SKILL.md

@@ -337,9 +337,11 @@ If the user corrects you, accept their answer and proceed with the corrected sta
   - "Astro"
   - "Other — I'll tell you"
 
-**WP-Q6 — Theme / plugin folder** (plain text): Scan `wp-content/themes/` and `wp-content/plugins/` for likely candidates first — present your best guess and let the user confirm or correct it. Ask — "Which theme or plugin should I focus on? (e.g. `wp-content/themes/my-theme` or `wp-content/plugins/my-plugin`)"
+**WP-Q6 — Theme / plugin folder(s)** (plain text): Scan `wp-content/themes/` and `wp-content/plugins/` for likely candidates first — present your best guess and let the user confirm or correct it. Ask — "Which theme or plugin should I focus on? You can provide multiple paths if they work together. (e.g. `wp-content/themes/my-theme, wp-content/plugins/my-plugin`)"
 
-Once WP-Q6 is answered, the **focus path** is now the theme/plugin folder — not the WP install root. All subsequent analysis, docs placement, and git root detection use this path as the base.
+Once WP-Q6 is answered, the confirmed paths become the **focus paths**. All subsequent analysis, docs placement, and git root detection are scoped to these paths — the WP install root is off-limits.
+
+**Each focus path must be its own git repository.** Git root detection (below) will validate this for every path provided. If any path is missing a `.git`, halt and ask the user to resolve it before continuing — do not proceed with a partial set.
 
 Store all WP answers and carry them through the rest of generate mode. They affect codebase analysis (Step 2) and the doc structure proposal (Step 3).
 
@@ -347,10 +349,10 @@ Store all WP answers and carry them through the rest of generate mode. They affe
 
 #### Git root detection (all stacks)
 
-**For WordPress:** run this check against the theme/plugin path confirmed in WP-Q6.
+**For WordPress:** run this check against every path confirmed in WP-Q6.
 **For all other stacks:** run this check against the detected codebase root (current working directory unless corrected above).
 
-Check for a `.git` directory at **that exact path**:
+For each focus path, check for a `.git` directory at **that exact path**:
 
 ```bash
 ls FOCUS_PATH/.git
@@ -358,20 +360,14 @@ ls FOCUS_PATH/.git
 
 Do not check parent folders — the `.git` must be in the specific folder being documented. For WordPress this means checking inside `wp-content/themes/my-theme/` or `wp-content/plugins/my-plugin/`, not in `wp-content/themes/`, `wp-content/`, or the WP install root.
 
-**If `.git` is found at the focus path:** no question needed — the repo root and focus path are the same. Proceed.
-
-**If `.git` is not found:** ask:
+**If `.git` is found:** no question needed — the repo root and focus path are the same. Proceed.
 
-- header: "Git root"
-- question: "I didn't find a `.git` folder at [FOCUS_PATH]. Where is the git root for this project?"
-- options:
-  - "It's at the WP install root (the folder I was invoked from)"
-  - "It's somewhere else — I'll tell you the path"
-  - "There's no git repo yet"
+**If `.git` is not found:** halt and tell the user:
+> "I didn't find a `.git` folder at [FOCUS_PATH]. Each documented path must be its own git repository. Please initialise a repo there and come back, or remove this path from the list."
 
-Then ask as plain text — "Where inside the git repo should the docs folder and VitePress config live? (Default: `docs/` inside [FOCUS_PATH].)"
+Do not continue until every focus path has a confirmed `.git`. Each path gets its own independent docs output, manifest, and GitHub Actions workflow.
 
-This matters because the GitHub Actions workflow file must go in `.github/workflows/` at the **git root**, even if the VitePress config and docs folder live deeper inside it (e.g. inside the theme or plugin subfolder).
+This matters because the GitHub Actions workflow file must go in `.github/workflows/` at the **git root** of each respective path.
 
 ---
 
@@ -404,6 +400,14 @@ Wait for all answers.
 
 ### Step 2 — Analyze the codebase
 
+#### Scope rule
+
+**Single focus path:** analysis is strictly confined to that directory. Do not read, Glob, or Grep anywhere outside it — including the WP install root, other themes, other plugins, or WP core.
+
+**Multiple focus paths:** analysis is confined to the declared paths combined. Cross-reading between them is allowed and expected — if the theme references a function from the plugin, follow that reference. Nothing outside the declared set is fair game.
+
+In both cases: if a file inside a focus path imports or references something outside the declared paths, read only that specific referenced file — do not expand analysis to its parent directory.
+
 Scan the codebase systematically. Build a mental map before writing anything. Look for:
 
 **For user-facing docs:**