@ngocsangairvds/vsaf 3.2.7 → 3.2.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ngocsangairvds/vsaf",
-  "version": "3.2.7",
+  "version": "3.2.8",
   "description": "improve confluence format",
   "keywords": ["claude", "claude-code", "ai", "sdlc", "framework", "bmad", "gitnexus", "superpowers"],
   "bin": {

package/tools/skills/vds-scripts-skill/SKILL.md

@@ -18,9 +18,7 @@ metadata:
 
 Use this skill as the **platform-routing entrypoint** for the WHO scripts ecosystem.
 
-`WHO-project` is the canonical VDS ecosystem for both reusable skills and routed scripts:
-- skills live under `WHO-project/vds-skills/skills/`
-- scripts and orchestrators live under `WHO-project/vds-scripts/`
+The VDS scripts ecosystem lives at `~/.claude/vds-scripts/` (installed via `vsaf global`).
 
 This skill helps you:
 - find the right `vds-cli` command family
@@ -46,27 +44,22 @@ Do **not** use this skill as the authoritative deep runbook for:
 
 ## Canonical Sources
 
-- Scripts workspace: `WHO-project/vds-scripts/`
-- Skills catalog: `WHO-project/vds-skills/skills/`
-- Skill registry: `WHO-project/vds-skills/registry.yaml`
-- Alignment workflow: `WHO-project/vds-skills/ALIGNMENT.md`
+- Scripts workspace: `~/.claude/vds-scripts/`
 
 ## Primary Command Entry Points
 
-```/dev/null/vds-scripts-skill-entrypoints.sh#L1-12
-# Interactive monorepo-root usage
-./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package vds-cli vds-cli --help
-./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package audit_orchestrator vds-audit --help
-./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package spec_orchestrator vds-spec --help
-
-# Dedicated vds-scripts worktree usage
-./scripts/worktree_uv.sh run --package vds_cli vds-cli --help
-./scripts/worktree_uv.sh run --package audit_orchestrator vds-audit --help
-./scripts/worktree_uv.sh run --package spec_orchestrator vds-spec --help
-
-# Maintained shell scripts must not copy the plain patterns above.
-# They should source scripts/vds_sh_helpers.sh and use vds_uv_run_package
-# / vds_uv_sync_package / vds_uv_sync_all instead.
+```bash
+# Via vds-cli (recommended — MCP-registered)
+vds-cli --help
+vds-cli confluence --help
+vds-cli jira --help
+vds-cli bitbucket --help
+vds-cli git --help
+
+# Direct uv invocation from vds-scripts root
+~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package vds-cli vds-cli --help
+~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package audit_orchestrator vds-audit --help
+~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package spec_orchestrator vds-spec --help
 ```
 
 ## Platform Command Families
@@ -128,8 +121,6 @@ Use these bundled references for depth:
 
 ## Notes
 
-- Edit this skill only under `WHO-project/vds-skills/skills/vds-scripts-skill/`.
-- Do not edit `.agent/skills/` directly.
 - Keep this file concise and routing-oriented; push deeper command catalogs into `references/`.
-- For integrated `WHO-project/vds-scripts` workspace usage, Python 3.14+ is the preferred baseline for humans and AI agents.
-- After updates, sync generated agent surfaces from the monorepo root.
+- For integrated `~/.claude/vds-scripts` workspace usage, Python 3.10+ is the preferred baseline.
+- After updates, re-run `vsaf global` to sync skills to all agent surfaces.

package/tools/skills/vds-scripts-skill/references/google-sheets.md

@@ -64,10 +64,8 @@ vds-cli google-sheets -- --json-only read \
 
 Interactive monorepo-root usage commonly uses:
 
-```/dev/null/google-sheets-prefix.sh#L1-1
-./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package vds-cli vds-cli google-sheets <command>
+```bash
+vds-cli google-sheets <command>
+# Or direct uv invocation:
+~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package vds-cli vds-cli google-sheets <command>
 ```
-
-Inside a dedicated `vds-scripts` worktree, the equivalent form is `./scripts/worktree_uv.sh run --package vds_cli vds-cli google-sheets <command>`.
-
-For maintained shell scripts inside `WHO-project/vds-scripts`, do not copy raw operator forms. Source `scripts/vds_sh_helpers.sh` and use the helper contract instead.

package/tools/skills/vds-scripts-skill/references/integration-commands.md

@@ -2,10 +2,10 @@
 
 vds Representative WHO integration command families.
 
-These examples are interactive operator examples. From the umbrella monorepo root, prefer `./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package <uv-package-name> ...`. Inside a dedicated `vds-scripts` worktree, prefer `./scripts/worktree_uv.sh run --package <member-dir> ...`. Maintained shell scripts inside `WHO-project/vds-scripts` should source `scripts/vds_sh_helpers.sh` instead of copying raw operator forms.
+These examples use `vds-cli` (MCP-registered entrypoint). For direct uv invocation, prefer `~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package <uv-package-name> ...`.
 
 - `vds-cli jira ...`
-  - JQL search example: `./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package jira_orchestrator vds-jira-cli search "project = CBDC ORDER BY updated DESC" --limit 5 --json-only`
+  - JQL search example: `vds-cli jira search "project = CBDC ORDER BY updated DESC" --limit 5 --json-only`
   - Note: `vds-jira-cli search` now accepts `--json-only` as a command-local flag after `search`, in addition to the global pre-subcommand form.
 - `vds-cli confluence ...`
 - `vds-cli bitbucket ...`