pan-stack-cli 0.1.4 → 0.2.1

package/lib/ui/workspace.js

@@ -0,0 +1,213 @@
+// lib/ui/workspace.js — monorepo scan cho `pan ui` (§4.7): tìm workspace root, quét
+// mọi app.panui.yaml (KHÔNG dùng `repositories:` trong .project.yaml), chọn dự án,
+// đọc/ghi khối `backend: { id, apiUrl }` trong app.panui.yaml.
+const fs = require("fs");
+const path = require("path");
+const { findNearestProjectManifest } = require("../discover");
+const { menuSelect } = require("../menu-prompt");
+const { t } = require("../i18n");
+
+const IGNORE_DIRS = new Set(["node_modules", ".git", "dist", ".codegen-check"]);
+const MAX_DEPTH = 5;
+const APP_YAML_NAME = "app.panui.yaml";
+
+/**
+ * Tìm workspace root bằng walkUp `.project.yaml` (tái dùng lib/discover.js).
+ * @param {string} [cwd]
+ * @returns {string|null}
+ */
+function findWorkspaceRoot(cwd = process.cwd()) {
+  const manifestPath = findNearestProjectManifest(cwd);
+  return manifestPath ? path.dirname(manifestPath) : null;
+}
+
+/**
+ * Quét đệ quy tối đa MAX_DEPTH cấp từ root, tìm mọi app.panui.yaml.
+ * @param {string} root
+ * @returns {Array<{ appYamlPath: string, dir: string, name: string }>}
+ */
+function scanPanuiProjects(root) {
+  const results = [];
+
+  function walk(dir, depth) {
+    if (depth > MAX_DEPTH) {
+      return;
+    }
+    let entries;
+    try {
+      entries = fs.readdirSync(dir, { withFileTypes: true });
+    } catch {
+      return;
+    }
+
+    for (const entry of entries) {
+      if (entry.name.startsWith(".") && entry.name !== ".") {
+        // vẫn cho phép quét vào các thư mục ẩn không nằm trong IGNORE_DIRS? Không —
+        // giữ đơn giản: bỏ mọi thư mục ẩn để tránh .git, .cache, ... rơi vào quét.
+        if (entry.isDirectory()) {
+          continue;
+        }
+      }
+      const fullPath = path.join(dir, entry.name);
+      if (entry.isDirectory()) {
+        if (IGNORE_DIRS.has(entry.name)) {
+          continue;
+        }
+        walk(fullPath, depth + 1);
+        continue;
+      }
+      if (entry.isFile() && entry.name === APP_YAML_NAME) {
+        results.push({
+          appYamlPath: fullPath,
+          dir,
+          name: path.basename(dir),
+        });
+      }
+    }
+  }
+
+  walk(root, 0);
+  return results;
+}
+
+/**
+ * @param {Array<{ appYamlPath: string, dir: string, name: string }>} projects
+ * @returns {Promise<{ appYamlPath: string, dir: string, name: string }>}
+ */
+async function selectProject(projects) {
+  if (!projects || projects.length === 0) {
+    throw new Error(
+      `Không tìm thấy dự án panui nào (không có ${APP_YAML_NAME} trong workspace, quét tối đa ${MAX_DEPTH} cấp).`
+    );
+  }
+  if (projects.length === 1) {
+    return projects[0];
+  }
+
+  const message = `Chọn dự án panui (${projects.length} dự án):`;
+  const choices = projects.map((p) => ({
+    name: `${p.name}  (${path.relative(process.cwd(), p.appYamlPath)})`,
+    value: p.appYamlPath,
+  }));
+  const hotkeys = [{ key: "x", label: t("EXIT_LABEL"), value: "__exit__" }];
+
+  let choice;
+  try {
+    choice = await menuSelect({ message, choices, hotkeys });
+  } catch (err) {
+    if (String(err && err.message) !== "no-core") throw err;
+    const inq = await import("@inquirer/prompts").catch(() => null);
+    if (!inq || typeof inq.select !== "function") {
+      throw new Error(
+        "Nhiều dự án panui — cần TTY để chọn (không tìm thấy @inquirer/prompts)."
+      );
+    }
+    choice = await inq.select({
+      message,
+      choices: [...choices, new inq.Separator(), { name: `x  ${t("EXIT_LABEL")}`, value: "__exit__" }],
+      loop: false,
+    });
+  }
+  if (choice === "__exit__") {
+    console.log(t("EXITED"));
+    process.exit(0);
+  }
+  return projects.find((p) => p.appYamlPath === choice);
+}
+
+/**
+ * Đọc khối `backend: { id, apiUrl }` trong app.panui.yaml (parser tối thiểu —
+ * chỉ hỗ trợ khối phẳng 2 dòng con `id:`/`apiUrl:` thụt lề 2 khoảng trắng).
+ * @param {string} appYamlPath
+ * @returns {{ id: string, apiUrl: string } | null}
+ */
+function readBackendId(appYamlPath) {
+  if (!fs.existsSync(appYamlPath)) {
+    return null;
+  }
+  const lines = fs.readFileSync(appYamlPath, "utf8").split(/\r?\n/);
+  let inBackend = false;
+  const result = {};
+  for (const rawLine of lines) {
+    if (!rawLine.trim()) {
+      continue;
+    }
+    const indent = rawLine.length - rawLine.trimStart().length;
+    const text = rawLine.trim();
+    if (indent === 0) {
+      inBackend = text.replace(/:$/, "") === "backend";
+      continue;
+    }
+    if (inBackend && indent === 2) {
+      const idx = text.indexOf(":");
+      if (idx < 0) continue;
+      const key = text.slice(0, idx).trim();
+      let value = text.slice(idx + 1).trim();
+      if (
+        (value.startsWith('"') && value.endsWith('"')) ||
+        (value.startsWith("'") && value.endsWith("'"))
+      ) {
+        value = value.slice(1, -1);
+      }
+      if (key === "id" || key === "apiUrl") {
+        result[key] = value;
+      }
+    }
+  }
+  return result.id || result.apiUrl ? result : null;
+}
+
+/**
+ * Ghi/cập nhật khối `backend: { id, apiUrl }` trong app.panui.yaml, giữ nguyên
+ * mọi nội dung khác của file (thay thế khối backend cũ nếu có, nếu không thì
+ * append vào cuối file).
+ * @param {string} appYamlPath
+ * @param {{ id: string, apiUrl: string }} backend
+ */
+function writeBackendId(appYamlPath, { id, apiUrl }) {
+  const original = fs.existsSync(appYamlPath)
+    ? fs.readFileSync(appYamlPath, "utf8")
+    : "";
+  const lines = original.length ? original.split(/\r?\n/) : [];
+
+  const newBlock = ["backend:", `  id: ${id}`, `  apiUrl: ${apiUrl}`];
+
+  let start = -1;
+  let end = -1;
+  for (let i = 0; i < lines.length; i += 1) {
+    const trimmed = lines[i].trim();
+    const indent = lines[i].length - lines[i].trimStart().length;
+    if (indent === 0 && trimmed.replace(/:$/, "") === "backend") {
+      start = i;
+      end = i + 1;
+      while (end < lines.length) {
+        const nextIndent = lines[end].length - lines[end].trimStart().length;
+        if (!lines[end].trim() || nextIndent > 0) {
+          end += 1;
+          continue;
+        }
+        break;
+      }
+      break;
+    }
+  }
+
+  let updatedLines;
+  if (start >= 0) {
+    updatedLines = [...lines.slice(0, start), ...newBlock, ...lines.slice(end)];
+  } else {
+    updatedLines = lines.length ? [...lines, "", ...newBlock] : [...newBlock];
+  }
+
+  fs.mkdirSync(path.dirname(appYamlPath), { recursive: true });
+  fs.writeFileSync(appYamlPath, `${updatedLines.join("\n")}\n`, "utf8");
+}
+
+module.exports = {
+  APP_YAML_NAME,
+  findWorkspaceRoot,
+  scanPanuiProjects,
+  selectProject,
+  readBackendId,
+  writeBackendId,
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pan-stack-cli",
-  "version": "0.1.4",
+  "version": "0.2.1",
   "description": "PAN Stack CLI — multi-repo git and project commands from .project.yaml",
   "license": "MIT",
   "bin": {
@@ -8,12 +8,16 @@
   },
   "files": [
     "bin",
-    "lib",
-    "templates"
+    "lib"
   ],
   "engines": {
     "node": ">=18"
   },
+  "dependencies": {
+    "@inquirer/core": "^11.2.1",
+    "@inquirer/prompts": "^8.5.2",
+    "serve": "^14.2.4"
+  },
   "keywords": [
     "pan-stack",
     "monorepo",
@@ -24,5 +28,8 @@
     "type": "git",
     "url": "https://github.com/doiya46/pan-stack.git",
     "directory": ".pan/pan-stack-cli"
+  },
+  "devDependencies": {
+    "@inquirer/testing": "^3.3.9"
   }
 }

package/templates/workspace/.claude/skills/writing-guidelines/SKILL.md

@@ -1,48 +0,0 @@
----
-name: writing-guidelines
-description: Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
-metadata:
-  author: vercel
-  version: "1.0.0"
-  argument-hint: <file-or-pattern>
----
-
-# Writing Guidelines
-
-Review files for compliance with Writing Guidelines.
-
-## How It Works
-
-1. Fetch the latest guidelines from the source URL below
-2. Read the specified files (or prompt user for files/pattern)
-3. Check against all rules in the fetched guidelines
-4. Output findings in the terse `file:line` format
-
-## Guidelines Source
-
-Fetch fresh guidelines before each review:
-
-```text
-https://raw.githubusercontent.com/vercel-labs/writing-guidelines/main/command.md
-```
-
-Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.
-
-## Local Markdown Rules
-
-Also check generated or edited Markdown against local markdownlint conventions:
-
-- Keep at most one blank line between blocks. Do not create multiple consecutive blank lines. This avoids `MD012/no-multiple-blanks`.
-- Use language tags on fenced code blocks.
-- Before finishing edits, scan changed Markdown files for repeated blank lines.
-
-## Usage
-
-When a user provides a file or pattern argument:
-1. Fetch guidelines from the source URL above
-2. Read the specified files
-3. Apply all rules from the fetched guidelines
-4. Apply the local Markdown rules above
-5. Output findings using the format specified in the guidelines
-
-If no files specified, ask the user which files to review.

package/templates/workspace/.codex/skills/writing-guidelines/SKILL.md

@@ -1,48 +0,0 @@
----
-name: writing-guidelines
-description: Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
-metadata:
-  author: vercel
-  version: "1.0.0"
-  argument-hint: <file-or-pattern>
----
-
-# Writing Guidelines
-
-Review files for compliance with Writing Guidelines.
-
-## How It Works
-
-1. Fetch the latest guidelines from the source URL below
-2. Read the specified files (or prompt user for files/pattern)
-3. Check against all rules in the fetched guidelines
-4. Output findings in the terse `file:line` format
-
-## Guidelines Source
-
-Fetch fresh guidelines before each review:
-
-```text
-https://raw.githubusercontent.com/vercel-labs/writing-guidelines/main/command.md
-```
-
-Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.
-
-## Local Markdown Rules
-
-Also check generated or edited Markdown against local markdownlint conventions:
-
-- Keep at most one blank line between blocks. Do not create multiple consecutive blank lines. This avoids `MD012/no-multiple-blanks`.
-- Use language tags on fenced code blocks.
-- Before finishing edits, scan changed Markdown files for repeated blank lines.
-
-## Usage
-
-When a user provides a file or pattern argument:
-1. Fetch guidelines from the source URL above
-2. Read the specified files
-3. Apply all rules from the fetched guidelines
-4. Apply the local Markdown rules above
-5. Output findings using the format specified in the guidelines
-
-If no files specified, ask the user which files to review.

package/templates/workspace/.cursor/skills/writing-guidelines/SKILL.md

@@ -1,48 +0,0 @@
----
-name: writing-guidelines
-description: Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
-metadata:
-  author: vercel
-  version: "1.0.0"
-  argument-hint: <file-or-pattern>
----
-
-# Writing Guidelines
-
-Review files for compliance with Writing Guidelines.
-
-## How It Works
-
-1. Fetch the latest guidelines from the source URL below
-2. Read the specified files (or prompt user for files/pattern)
-3. Check against all rules in the fetched guidelines
-4. Output findings in the terse `file:line` format
-
-## Guidelines Source
-
-Fetch fresh guidelines before each review:
-
-```text
-https://raw.githubusercontent.com/vercel-labs/writing-guidelines/main/command.md
-```
-
-Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.
-
-## Local Markdown Rules
-
-Also check generated or edited Markdown against local markdownlint conventions:
-
-- Keep at most one blank line between blocks. Do not create multiple consecutive blank lines. This avoids `MD012/no-multiple-blanks`.
-- Use language tags on fenced code blocks.
-- Before finishing edits, scan changed Markdown files for repeated blank lines.
-
-## Usage
-
-When a user provides a file or pattern argument:
-1. Fetch guidelines from the source URL above
-2. Read the specified files
-3. Apply all rules from the fetched guidelines
-4. Apply the local Markdown rules above
-5. Output findings using the format specified in the guidelines
-
-If no files specified, ask the user which files to review.

package/templates/workspace/.pan.yaml

@@ -1,25 +0,0 @@
-# Workspace-level commands. Per-repo commands live in apps/*/.pan.yaml
-commands:
-  install:
-    alias: i
-    description: Install dependencies across cloned repositories
-    shell: |
-      set -euo pipefail
-      root="${PAN_WORKSPACE_ROOT}"
-      for dir in apps/web apps/api; do
-        [[ -d "$root/$dir" ]] || { echo "Missing: $root/$dir (run 'pan clone' first?)" >&2; exit 1; }
-        echo "-> install $dir"
-        (cd "$root/$dir" && npm install)
-      done
-      echo "Done."
-
-  test:
-    default: web
-    description: Run tests (web | api)
-    targets:
-      web:
-        cwd: apps/web
-        exec: npm test
-      api:
-        cwd: apps/api
-        exec: npm test

package/templates/workspace/.project.yaml

@@ -1,15 +0,0 @@
-project: __PROJECT_NAME__
-managed_by: your-team
-
-stack:
-  repo: repo_url_to_be_filled
-
-repositories:
-  - name: bookshop-web
-    description: Customer-facing web application
-    url: repo_url_to_be_filled
-    path: apps/web
-  - name: bookshop-api
-    description: REST API service
-    url: repo_url_to_be_filled
-    path: apps/api

package/templates/workspace/README.md

@@ -1,35 +0,0 @@
-# __PROJECT_NAME__
-
-PAN Stack workspace shell for the Bookshop example project.
-
-This repository is the **coordination layer** — not the product source tree. It holds
-agent skills, workspace manifests, and `pan` commands. Product code lives in the
-repositories listed in `.project.yaml`.
-
-## Layout
-
-```text
-__PROJECT_NAME__/
-  .project.yaml          # Workspace manifest (repository list)
-  .pan.yaml              # Workspace-level pan commands
-  .claude/skills/        # Claude Code skills
-  .cursor/skills/        # Cursor agent skills
-  .codex/skills/         # Codex agent skills
-  apps/
-    web/                 # bookshop-web (after pan clone)
-    api/                 # bookshop-api (after pan clone)
-```
-
-## Quick start
-
-```bash
-# Edit repository URLs in .project.yaml, then:
-pan clone
-pan install
-pan test web
-```
-
-## Agent skills
-
-All three agent folders ship with the shared `writing-guidelines` skill. Add more
-skills under each `.claude`, `.cursor`, and `.codex` directory as your team grows.