@haus-tech/haus-workflow 0.18.1 → 0.19.0

package/library/catalog/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "2.6.1",
+  "version": "2.6.2",
   "items": [
     {
       "id": "haus.nextjs-patterns",

package/library/global/commands/haus-clone.md

@@ -0,0 +1,32 @@
+Clone repositories for this project. Per-repo setup (install, Docker, `.env`) is a separate step that isn't wired yet — this command only gets repos onto disk.
+
+Cloning a single repo is always `haus clone <url> [dir]`. This command picks _which_ repos to clone and runs that primitive for each. There are two modes, chosen by whether a name was given.
+
+## Mode A — a project name was given (`project:clone <name>`)
+
+Find one repo by name on GitHub and clone it. Does **not** require a workspace or `repos.manifest.json`.
+
+1. Make sure GitHub CLI is ready: run `gh auth status`. If not authenticated, tell the user to run `gh auth login` and stop.
+2. Scope the search to repos the user owns or belongs to: get their login with `gh api user -q .login` and their orgs with `gh api user/orgs -q '.[].login'`.
+3. Search by name, passing one `--owner` per login/org from step 2:
+   `gh search repos "<name>" --match name --limit 10 --json fullName,description,url,isPrivate,pushedAt --owner <login> [--owner <org> …]`
+   If that returns nothing, retry **without** `--owner` (a broader, all-of-GitHub search) and tell the user you widened it.
+4. Decide from the results:
+   - **0 matches** — tell the user nothing matched `<name>`; offer to try a different name or broaden. Stop.
+   - **1 match** — show `fullName` + description and confirm "Clone this one?" before proceeding.
+   - **2+ matches** — use `AskUserQuestion` to let the user pick which repo (list each `fullName` with its description; private repos noted). Include a final option like "None of these — search again / broaden" so they can refine.
+5. Clone the chosen repo with `haus clone <url> [dir]`, using the `url` from the search result. Default target is a folder named after the repo under the current directory; confirm where it will land before running. Quote the exact command first.
+6. Report the result (cloned / skipped if already present / failed). Remind the user that installing dependencies and configuring the repo is still a manual step for now.
+
+## Mode B — no name was given (`project:clone`)
+
+Clone a whole **workspace** from its manifest. Workspace-only (a `repos.manifest.json` at the repo root); for a lone repo without a manifest, use Mode A with a name instead.
+
+1. Confirm `repos.manifest.json` exists at the workspace root. If not, tell the user this mode is for multi-repo workspaces (or they can pass a `<name>` to clone a single repo) and stop.
+2. Read `repos.manifest.json`. Each entry has an `id`, a `folder`, and a git URL (`repo`). If entries have no `repo` URL, ask the user to add them (or supply the URLs) — `haus clone` needs a URL per repo.
+3. Read `repos.local.json` if present — its `pathOverrides` map (`folder` → absolute path) marks repos the user already has locally.
+4. Ask the user, via `AskUserQuestion`, how to obtain the repos:
+   - **Clean clone** — clone every manifest repo fresh into its `folder` under the workspace.
+   - **Reuse local** — skip any repo already in `repos.local.json` `pathOverrides`; clone only the rest.
+5. For each repo to clone, run (quoting it first): `haus clone <repo-url> <folder>` from the workspace root. Offer `--dry-run` first if the user wants a preview. If one repo fails, report it and continue to the next.
+6. After the loop, report which repos were cloned, skipped (already present or reused local), and failed. Remind the user that installing dependencies and configuring each repo (`.env`, services) is still a manual step for now.

package/library/global/skills/haus-workflow/SKILL.md

@@ -21,15 +21,16 @@ The unprefixed verbs (`update`, `catalog`, `install`, `uninstall`) act on **this
 haus install** (`~/.claude`, npm) — they manage the haus tool itself, like `npm install -g`.
 The short legacy aliases still work but the names below are canonical.
 
-| Task name (legacy aliases)                                        | Command                 | Scope   | What it does                                                                                |
-| ----------------------------------------------------------------- | ----------------------- | ------- | ------------------------------------------------------------------------------------------- |
-| `project:init` (`setup`, `init`)                                  | _Setup procedure below_ | project | First-time setup of an **existing** repo: adds AI skills, commands, workflow + project docs |
-| `project:refresh` (`apply`, `refresh`, `claude-md`, `regenerate`) | `haus apply --write`    | project | Re-run setup / refresh `.claude/` context + regenerate root `CLAUDE.md` import block        |
-| `project:doctor` (`doctor`, `check`)                              | `haus doctor`           | project | Check for install drift                                                                     |
-| `update` (`upgrade`)                                              | `haus update`           | global  | Update npm package + catalog + `~/.claude/` (also refreshes this project)                   |
-| `catalog`                                                         | `haus update`           | global  | Fetch latest catalog (same command as update)                                               |
-| `install` (`global`)                                              | `haus install`          | global  | Seed `~/.claude/` with haus-owned files                                                     |
-| `uninstall`                                                       | `haus uninstall`        | global  | Remove all haus global files from `~/.claude/`                                              |
+| Task name (legacy aliases)                                        | Command                 | Scope   | What it does                                                                                                                |
+| ----------------------------------------------------------------- | ----------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------- |
+| `project:init` (`setup`, `init`)                                  | _Setup procedure below_ | project | First-time setup of an **existing** repo: adds AI skills, commands, workflow + project docs                                 |
+| `project:clone [name]` (`clone`)                                  | _Clone procedure below_ | project | No name: clone a **workspace**'s repos from `repos.manifest.json`. With a `name`: find & clone one repo by name from GitHub |
+| `project:refresh` (`apply`, `refresh`, `claude-md`, `regenerate`) | `haus apply --write`    | project | Re-run setup / refresh `.claude/` context + regenerate root `CLAUDE.md` import block                                        |
+| `project:doctor` (`doctor`, `check`)                              | `haus doctor`           | project | Check for install drift                                                                                                     |
+| `update` (`upgrade`)                                              | `haus update`           | global  | Update npm package + catalog + `~/.claude/` (also refreshes this project)                                                   |
+| `catalog`                                                         | `haus update`           | global  | Fetch latest catalog (same command as update)                                                                               |
+| `install` (`global`)                                              | `haus install`          | global  | Seed `~/.claude/` with haus-owned files                                                                                     |
+| `uninstall`                                                       | `haus uninstall`        | global  | Remove all haus global files from `~/.claude/`                                                                              |
 
 ## Step 1 — Determine the task
 
@@ -48,6 +49,8 @@ Options:
      (haus update — checks npm for new version, fetches catalog, refreshes ~/.claude/)
   4. [global] catalog — fetch catalog updates only
      (haus update — same command; pulls latest workflow templates and lockfile)
+  5. [project] project:clone [name] — clone repos
+     (no name: clone a workspace from repos.manifest.json; with a name: find & clone one repo by name from GitHub)
 ```
 
 Map the user's selection to the command from the alias table, then continue to Step 2.
@@ -58,6 +61,8 @@ Run the mapped command via Bash. Quote the exact command you are running before
 
 **Exception — `project:init` (`setup` / `init`):** this maps to a multi-step procedure, not a single command. Do not run a bare `haus init`. Skip to **Setup (`project:init`)** under Step 3 and follow it.
 
+**Exception — `project:clone` (`clone`):** this asks the user a question before running, so it is a short procedure too. Skip to **Clone (`project:clone`)** under Step 3 and follow it.
+
 ## Step 3 — Post-run steps
 
 After the command completes, follow the relevant post-run steps below.
@@ -67,6 +72,10 @@ After the command completes, follow the relevant post-run steps below.
 1. Open and follow `~/.claude/commands/haus-setup.md` — the installed `haus-setup` command (in some projects also `.claude/commands/haus-setup.md`). Run every step in order. It detects the stack, asks the guided questions, runs `haus apply --write` (scaffolding, skills, commands, rules, docs skill), writes the **project docs** (`CLAUDE.md` body + `docs/`) and `.haus-workflow/deep-context.json`, runs `haus recommend`, applies the newly-matched helpers, and confirms.
 2. Then fill `.haus-workflow/workflow-config.md` — replace every placeholder (`TODO`, `n/a`, empty): test/lint/typecheck/build commands (check `package.json`), docs paths, validation library, pre-commit tool, highest-stakes logic (ask if unclear). Leave none.
 
+### Clone (`project:clone`)
+
+1. Open and follow `~/.claude/commands/haus-clone.md` — the installed `haus-clone` command. With a `name` argument it finds and clones one matching repo from GitHub; with no argument it clones a workspace's repos from `repos.manifest.json`. Per-repo setup (install, Docker, env) is a separate step that isn't wired yet, so just get the repos in place for now.
+
 ### After `haus apply --write`
 
 Verify that the root `CLAUDE.md` imports all three haus files:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haus-tech/haus-workflow",
-  "version": "0.18.1",
+  "version": "0.19.0",
   "description": "Haus AI workflow CLI for Claude Code.",
   "type": "module",
   "bin": {
@@ -16,7 +16,6 @@
     "scripts/postinstall.mjs",
     "library/global",
     "library/catalog",
-    "tests/fixtures/catalog",
     "README.md",
     "CHANGELOG.md"
   ],
@@ -26,16 +25,15 @@
     "test": "node --import tsx --test tests/**/*.test.js",
     "test:coverage": "c8 yarn test",
     "coverage:check": "c8 --check-coverage yarn test",
-    "lint": "eslint src scripts",
+    "lint": "eslint src",
     "format:check": "prettier --check .",
     "format": "prettier --write .",
     "typecheck": "tsc --noEmit",
-    "typecheck:scripts": "tsc --noEmit --project tsconfig.scripts.json",
     "pack:local": "yarn pack",
     "release": "GITHUB_TOKEN=$(gh auth token) release-it",
     "release:dry": "GITHUB_TOKEN=$(gh auth token) release-it --dry-run",
     "prepack": "yarn build",
-    "verify": "yarn typecheck && yarn typecheck:scripts && yarn lint && yarn build && yarn test",
+    "verify": "yarn typecheck && yarn lint && yarn build && yarn test",
     "verify:full": "yarn verify && yarn coverage:check",
     "postinstall": "node ./scripts/postinstall.mjs || true",
     "prepare": "lefthook install || true",
@@ -49,10 +47,8 @@
     "fast-glob": "3.3.3",
     "fs-extra": "11.3.5",
     "ignore": "6.0.2",
-    "picomatch": "4.0.4",
     "semver": "7.8.0",
-    "yaml": "2.8.4",
-    "zod": "3.25.76"
+    "yaml": "2.8.4"
   },
   "devDependencies": {
     "@release-it/conventional-changelog": "11.0.0",

package/tests/README.md

@@ -1,54 +0,0 @@
-# Tests
-
-Node built-in test runner (`node --test`). No framework. All test files are `.js` (compiled output not required — tests import from `dist/` via `fixture-runner.js`).
-
-```bash
-yarn test
-```
-
-## Structure
-
-| Path              | Contents                            |
-| ----------------- | ----------------------------------- |
-| `tests/*.test.js` | Unit and integration tests          |
-| `tests/helpers/`  | Shared test utilities               |
-| `tests/fixtures/` | Static fixture repos used by tests  |
-
-## helpers/fixture-runner.js
-
-Utilities for running the compiled CLI against fixture repos in a temp directory:
-
-- `cloneFixtureToTemp(fixtureName)` — copies `tests/fixtures/repos/<name>` to a temp dir, returns the path
-- `runHaus(cwd, command)` — runs `node dist/cli.js <command>` in `cwd`, returns stdout
-- `readHausJson(cwd, fileName)` — reads `.haus-workflow/<fileName>` as parsed JSON
-
-Tests that use `fixture-runner.js` require a built `dist/` — run `yarn build && yarn test`, or use `yarn verify` which builds before running tests.
-
-## fixtures/
-
-### fixtures/repos/
-
-Full fixture repos scanned by integration tests and golden tests. Each subdirectory is a minimal repo skeleton:
-
-| Fixture                          | Stack                                 |
-| -------------------------------- | ------------------------------------- |
-| `laravel-app`                    | Laravel (PHP, Composer, PHPUnit)      |
-| `laravel-with-react-frontend`    | Laravel + React (pnpm)                |
-| `nest-graphql-api`               | NestJS + GraphQL (Yarn)               |
-| `nextjs-app`                     | Next.js (pnpm)                        |
-| `nx-workspace`                   | Nx monorepo (Yarn)                    |
-| `orphan-graphql-config`          | GraphQL config without backend (pnpm) |
-| `turbo-monorepo`                 | Turborepo (Yarn)                      |
-| `vendure-monorepo`               | Vendure e-commerce (Yarn)             |
-| `vendure-with-nextjs-storefront` | Vendure + Next.js storefront (Yarn)   |
-| `wordpress-bedrock-site`         | WordPress Bedrock (Composer)          |
-| `wordpress-with-node-tooling`    | WordPress + Node tooling (pnpm)       |
-
-### Other fixture dirs
-
-- `fixtures/dotnet-service/` — unsupported stack (C#/.NET), used to verify unsupported-stack handling
-- `fixtures/unsupported-go/` — unsupported stack (Go)
-- `fixtures/unsupported-python/` — unsupported stack (Python)
-- `fixtures/vendure-plugin/` — minimal Vendure plugin package
-- `fixtures/laravel-app/`, `fixtures/next-react-app/`, `fixtures/wordpress-bedrock/` — legacy shallow fixtures; prefer `fixtures/repos/` equivalents for new tests
-

package/tests/fixtures/catalog/agents/code-reviewer.md

@@ -1,15 +0,0 @@
----
-description: Fixture stub agent for CLI tests.
----
-
-## Use when
-
-Use when working on the relevant task.
-
-## Do not use when
-
-Do not use for unrelated tasks.
-
-## Verification
-
-Check that the output matches expectations.

package/tests/fixtures/catalog/agents/docs-researcher.md

@@ -1,15 +0,0 @@
----
-description: Fixture stub agent for CLI tests.
----
-
-## Use when
-
-Use when working on the relevant task.
-
-## Do not use when
-
-Do not use for unrelated tasks.
-
-## Verification
-
-Check that the output matches expectations.

package/tests/fixtures/catalog/agents/planner.md

@@ -1,15 +0,0 @@
----
-description: Fixture stub agent for CLI tests.
----
-
-## Use when
-
-Use when working on the relevant task.
-
-## Do not use when
-
-Do not use for unrelated tasks.
-
-## Verification
-
-Check that the output matches expectations.

package/tests/fixtures/catalog/agents/security-reviewer.md

@@ -1,15 +0,0 @@
----
-description: Fixture stub agent for CLI tests.
----
-
-## Use when
-
-Use when working on the relevant task.
-
-## Do not use when
-
-Do not use for unrelated tasks.
-
-## Verification
-
-Check that the output matches expectations.

package/tests/fixtures/catalog/agents/test-reviewer.md

@@ -1,15 +0,0 @@
----
-description: Fixture stub agent for CLI tests.
----
-
-## Use when
-
-Use when working on the relevant task.
-
-## Do not use when
-
-Do not use for unrelated tasks.
-
-## Verification
-
-Check that the output matches expectations.