@haus-tech/haus-workflow 0.16.1 → 0.16.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +2 -0
- package/README.md +10 -6
- package/library/global/skills/haus-workflow/SKILL.md +22 -19
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.16.2](https://github.com/WeAreHausTech/haus-workflow/compare/v0.16.1...v0.16.2) (2026-06-09)
|
|
4
|
+
|
|
3
5
|
## [0.16.1](https://github.com/WeAreHausTech/haus-workflow/compare/v0.16.0...v0.16.1) (2026-06-09)
|
|
4
6
|
|
|
5
7
|
## [0.16.0](https://github.com/WeAreHausTech/haus-workflow/compare/v0.15.0...v0.16.0) (2026-06-05)
|
package/README.md
CHANGED
|
@@ -29,13 +29,17 @@ and configures the repo for you.
|
|
|
29
29
|
|
|
30
30
|
Once installed, Claude Code gains a `/haus-workflow` slash command.
|
|
31
31
|
|
|
32
|
+
The `project:*` tasks act on the current repo. The unprefixed verbs (`update`,
|
|
33
|
+
`catalog`, `install`, `uninstall`) manage the haus tool itself on your machine
|
|
34
|
+
(`~/.claude` + npm), like `npm install -g`. The short legacy names still work.
|
|
35
|
+
|
|
32
36
|
```
|
|
33
|
-
/haus-workflow
|
|
34
|
-
/haus-workflow
|
|
35
|
-
/haus-workflow
|
|
36
|
-
/haus-workflow
|
|
37
|
-
/haus-workflow
|
|
38
|
-
/haus-workflow
|
|
37
|
+
/haus-workflow # interactive menu — pick a task
|
|
38
|
+
/haus-workflow project:init # [project] add haus to an EXISTING repo — AI skills, commands, workflow + docs
|
|
39
|
+
/haus-workflow project:refresh # [project] refresh .claude/ and regenerate CLAUDE.md imports
|
|
40
|
+
/haus-workflow project:doctor # [project] health check for drift
|
|
41
|
+
/haus-workflow update # [global] update npm package + catalog + ~/.claude/
|
|
42
|
+
/haus-workflow catalog # [global] fetch only the latest catalog
|
|
39
43
|
```
|
|
40
44
|
|
|
41
45
|
Without an argument, the skill presents a menu so you can pick the task. With an argument, it runs immediately.
|
|
@@ -17,16 +17,21 @@ All-in-one entry point for the Haus AI workflow.
|
|
|
17
17
|
|
|
18
18
|
## Task aliases → commands
|
|
19
19
|
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
|
27
|
-
|
|
|
28
|
-
| `
|
|
29
|
-
| `claude-md`, `regenerate`
|
|
20
|
+
Task names use an asymmetric scope convention. The **project:** namespace marks tasks that
|
|
21
|
+
act on **this repo** (`./.claude`, `./.haus-workflow`) — type `project:` to see them all.
|
|
22
|
+
The unprefixed verbs (`update`, `catalog`, `install`, `uninstall`) act on **this machine's
|
|
23
|
+
haus install** (`~/.claude`, npm) — they manage the haus tool itself, like `npm install -g`.
|
|
24
|
+
The short legacy aliases still work but the names below are canonical.
|
|
25
|
+
|
|
26
|
+
| Task name (legacy aliases) | Command | Scope | What it does |
|
|
27
|
+
| ----------------------------------------------------------------- | ----------------------- | ------- | ------------------------------------------------------------------------------------------- |
|
|
28
|
+
| `project:init` (`setup`, `init`) | _Setup procedure below_ | project | First-time setup of an **existing** repo: adds AI skills, commands, workflow + project docs |
|
|
29
|
+
| `project:refresh` (`apply`, `refresh`, `claude-md`, `regenerate`) | `haus apply --write` | project | Re-run setup / refresh `.claude/` context + regenerate root `CLAUDE.md` import block |
|
|
30
|
+
| `project:doctor` (`doctor`, `check`) | `haus doctor` | project | Check for install drift |
|
|
31
|
+
| `update` (`upgrade`) | `haus update` | global | Update npm package + catalog + `~/.claude/` (also refreshes this project) |
|
|
32
|
+
| `catalog` | `haus update` | global | Fetch latest catalog (same command as update) |
|
|
33
|
+
| `install` (`global`) | `haus install` | global | Seed `~/.claude/` with haus-owned files |
|
|
34
|
+
| `uninstall` | `haus uninstall` | global | Remove all haus global files from `~/.claude/` |
|
|
30
35
|
|
|
31
36
|
## Step 1 — Determine the task
|
|
32
37
|
|
|
@@ -37,16 +42,14 @@ All-in-one entry point for the Haus AI workflow.
|
|
|
37
42
|
```
|
|
38
43
|
Question: "What would you like to do?"
|
|
39
44
|
Options:
|
|
40
|
-
1.
|
|
41
|
-
(
|
|
42
|
-
2.
|
|
45
|
+
1. [project] project:init — add haus to an existing project for the first time
|
|
46
|
+
(AI skills + commands + workflow into a repo you already have, then a deep read to write the CLAUDE.md docs body + docs/)
|
|
47
|
+
2. [project] project:refresh — refresh this project's setup
|
|
43
48
|
(haus apply --write — re-runs setup, regenerates CLAUDE.md imports)
|
|
44
|
-
3.
|
|
49
|
+
3. [global] update — update haus package + catalog + global files
|
|
45
50
|
(haus update — checks npm for new version, fetches catalog, refreshes ~/.claude/)
|
|
46
|
-
4.
|
|
51
|
+
4. [global] catalog — fetch catalog updates only
|
|
47
52
|
(haus update — same command; pulls latest workflow templates and lockfile)
|
|
48
|
-
5. Regenerate CLAUDE.md import block
|
|
49
|
-
(haus apply --write — rewrites the @-import block at the root CLAUDE.md)
|
|
50
53
|
```
|
|
51
54
|
|
|
52
55
|
Map the user's selection to the command from the alias table, then continue to Step 2.
|
|
@@ -55,13 +58,13 @@ Map the user's selection to the command from the alias table, then continue to S
|
|
|
55
58
|
|
|
56
59
|
Run the mapped command via Bash. Quote the exact command you are running before executing it.
|
|
57
60
|
|
|
58
|
-
**Exception — `setup` / `init
|
|
61
|
+
**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.
|
|
59
62
|
|
|
60
63
|
## Step 3 — Post-run steps
|
|
61
64
|
|
|
62
65
|
After the command completes, follow the relevant post-run steps below.
|
|
63
66
|
|
|
64
|
-
### Setup (`
|
|
67
|
+
### Setup (`project:init`)
|
|
65
68
|
|
|
66
69
|
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.
|
|
67
70
|
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.
|