@caddis/cli 0.4.93 → 0.4.94

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.
Files changed (55) hide show
  1. package/bundles/antigravity-plugin/guard_agy.py +6 -2
  2. package/bundles/antigravity-plugin/plugin.json +1 -1
  3. package/bundles/antigravity-plugin/repo_freshness.py +71 -6
  4. package/bundles/antigravity-plugin/repo_hygiene.py +516 -0
  5. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_exit.cpython-311.pyc +0 -0
  6. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_file_lock.cpython-311.pyc +0 -0
  7. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_frontmatter.cpython-311.pyc +0 -0
  8. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_redact.cpython-311.pyc +0 -0
  9. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_roadmap.cpython-311.pyc +0 -0
  10. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_rows.cpython-311.pyc +0 -0
  11. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_status.cpython-311.pyc +0 -0
  12. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_tidy.cpython-311.pyc +0 -0
  13. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_todo.cpython-311.pyc +0 -0
  14. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_workstreams.cpython-311.pyc +0 -0
  15. package/bundles/antigravity-plugin/scripts/__pycache__/caddis_worktree_safety.cpython-311.pyc +0 -0
  16. package/bundles/antigravity-plugin/scripts/caddis_finished.py +537 -0
  17. package/bundles/antigravity-plugin/scripts/caddis_guide.json +9 -8
  18. package/bundles/antigravity-plugin/scripts/caddis_own_cleanup.py +23 -248
  19. package/bundles/antigravity-plugin/scripts/caddis_repo_tidy.py +240 -0
  20. package/bundles/antigravity-plugin/scripts/caddis_tidy.py +12 -0
  21. package/bundles/antigravity-plugin/scripts/caddis_worktree_root.py +111 -2
  22. package/bundles/antigravity-plugin/scripts/setup_project_ai.py +67 -10
  23. package/bundles/antigravity-plugin/skills/_registry.md +4 -4
  24. package/bundles/antigravity-plugin/skills/adopt-app/SKILL.md +2 -5
  25. package/bundles/antigravity-plugin/skills/cloud-phases/SKILL.md +1 -1
  26. package/bundles/antigravity-plugin/skills/dashboard-perf-sweep/SKILL.md +1 -1
  27. package/bundles/antigravity-plugin/skills/db-diagram/SKILL.md +1 -1
  28. package/bundles/antigravity-plugin/skills/explainer-doc/SKILL.md +1 -1
  29. package/bundles/antigravity-plugin/skills/implement/SKILL.md +4 -0
  30. package/bundles/antigravity-plugin/skills/port-to-github/SKILL.md +2 -5
  31. package/bundles/antigravity-plugin/skills/pr-merge/SKILL.md +1 -1
  32. package/bundles/antigravity-plugin/skills/ship-merge/SKILL.md +1 -1
  33. package/bundles/antigravity-plugin/skills/ship-pr/SKILL.md +1 -1
  34. package/bundles/antigravity-plugin/skills/tech-explainer/SKILL.md +2 -6
  35. package/bundles/antigravity-plugin/skills/using-git-worktrees/SKILL.md +19 -2
  36. package/bundles/antigravity-plugin/skills/warm-editorial-ui/SKILL.md +1 -1
  37. package/bundles/antigravity-plugin-extras/plugin.json +1 -1
  38. package/bundles/antigravity-plugin-extras/skills/_registry.md +2 -2
  39. package/bundles/antigravity-plugin-extras/skills/building-ai-agent-on-cloudflare/SKILL.md +1 -2
  40. package/bundles/antigravity-plugin-extras/skills/building-mcp-server-on-cloudflare/SKILL.md +1 -2
  41. package/bundles/antigravity-plugin-extras/skills/data-contract-pipeline/SKILL.md +1 -1
  42. package/bundles/antigravity-plugin-extras/skills/responsive-mobile-native/SKILL.md +2 -4
  43. package/bundles/antigravity-plugin-extras/skills/runner-move/SKILL.md +2 -4
  44. package/bundles/antigravity-plugin-extras/skills/setup-project-ai/SKILL.md +1 -1
  45. package/bundles/antigravity-plugin-extras/skills/understand-anything/SKILL.md +2 -5
  46. package/bundles/codex/.codex/skills/coding/dashboard-perf-sweep/SKILL.md +1 -1
  47. package/bundles/codex/.codex/skills/data/db-diagram/SKILL.md +1 -1
  48. package/bundles/codex/.codex/skills/devops/adopt-app/SKILL.md +2 -5
  49. package/bundles/codex/.codex/skills/devops/port-to-github/SKILL.md +2 -5
  50. package/bundles/codex/.codex/skills/devops/using-git-worktrees/SKILL.md +19 -2
  51. package/bundles/codex/.codex/skills/docs/explainer-doc/SKILL.md +1 -1
  52. package/bundles/codex/.codex/skills/docs/tech-explainer/SKILL.md +2 -6
  53. package/bundles/codex/.codex/skills/frontend/warm-editorial-ui/SKILL.md +1 -1
  54. package/bundles/manifest.json +3 -3
  55. package/package.json +1 -1
@@ -24,6 +24,10 @@ stays where it is: moving it breaks a venv, which keeps absolute paths.
24
24
  CLI: `python caddis_worktree_root.py [--repo PATH] [--root PATH] [--record --purpose TEXT] <short-name>` prints the path.
25
25
  Exit 2 on a bad name or a folder that is not in a git repo.
26
26
 
27
+ `python caddis_worktree_root.py --bootstrap [--repo PATH]` runs INSIDE a linked worktree and gives it its own
28
+ dependencies (uv sync, or venv + pip; npm ci per package-lock.json). The pre-push gate needs that `.venv`.
29
+ Exit 0 done, 1 a step failed or a tool is missing, 2 not a linked worktree.
30
+
27
31
  `--record` also appends the path to this session's created list (`caddis_created.py`, by="helper"), so `/handoff` can
28
32
  remove the worktree later. The helper creates nothing, so the path is recorded as INTENDED: run `git worktree add` on the
29
33
  path it printed. A session with no session id, or a record that cannot be written, only prints a warning on stderr: the
@@ -34,6 +38,7 @@ from __future__ import annotations
34
38
 
35
39
  import argparse
36
40
  import os
41
+ import shutil
37
42
  import subprocess
38
43
  import sys
39
44
  from pathlib import Path
@@ -89,21 +94,125 @@ def worktree_path(repo: Path | str, short_name: str, root: Path | str | None = N
89
94
  """The path for a NEW worktree of `repo`: `<root>/<main checkout folder name>/<short_name>`. Creates nothing.
90
95
  `short_name` is one plain folder name: ValueError for an empty name, `.`, `..`, or one with a path separator or a
91
96
  colon (a drive such as `C:foo` would replace the root on Windows)."""
92
- if (not short_name or short_name in (".", "..") or any(c in short_name for c in "/\:")
97
+ if (not short_name or short_name in (".", "..") or any(c in short_name for c in "/\\:")
93
98
  or short_name != short_name.strip()):
94
99
  raise ValueError(f"the short name must be one plain folder name, not {short_name!r}")
95
100
  main = main_checkout(repo) # one git call
96
101
  return (_explicit_root(root) or main.parent / FALLBACK_DIR) / main.name / short_name
97
102
 
98
103
 
104
+ # ---- bootstrap: give a fresh worktree its own dependencies ---------------------------------------------------------
105
+ # A worktree installs its dependencies fresh. It never links or borrows a venv or node_modules from another folder
106
+ # (the main checkout's venv belongs to a running dev service and is often behind). The pre-push gate uses only the
107
+ # worktree's own `.venv`, so this is the one command that makes a new worktree pass it.
108
+
109
+ NPM_FOLDERS = (".", "frontend") # folders checked for a package-lock.json
110
+
111
+
112
+ def is_linked_worktree(repo: Path) -> bool:
113
+ """True when `repo` is inside a linked worktree (its git dir is not the common dir)."""
114
+ git_dir = _git_out(repo, "rev-parse", "--absolute-git-dir")
115
+ common = _git_out(repo, "rev-parse", "--git-common-dir")
116
+ if not git_dir or not common:
117
+ return False
118
+ return os.path.normcase(os.path.normpath(git_dir)) != os.path.normcase(os.path.normpath(repo / common))
119
+
120
+
121
+ def venv_python(venv: Path) -> Path:
122
+ """The interpreter inside a venv folder (Windows `Scripts/`, POSIX `bin/`)."""
123
+ win = venv / "Scripts" / "python.exe"
124
+ return win if win.exists() or os.name == "nt" else venv / "bin" / "python"
125
+
126
+
127
+ def _declares_dev_extra(pyproject: Path) -> tuple[bool, bool]:
128
+ """(has a [project] table, declares a `dev` optional-dependency group)."""
129
+ try:
130
+ import tomllib
131
+ data = tomllib.loads(pyproject.read_text(encoding="utf-8"))
132
+ except Exception: # noqa: BLE001 - unreadable or invalid TOML: treat as "declares nothing"
133
+ return False, False
134
+ project = data.get("project")
135
+ if not isinstance(project, dict):
136
+ return False, False
137
+ return True, "dev" in (project.get("optional-dependencies") or {})
138
+
139
+
140
+ def plan_bootstrap(root: Path) -> list[tuple[Path, list[str]]]:
141
+ """The commands (cwd, argv) that bootstrap the worktree at `root`. Reads files only; runs nothing.
142
+
143
+ Python: `uv sync --frozen --all-extras` when `uv.lock` exists (pip would not honour the lock), else `python -m venv .venv`
144
+ then `pip install` of what the repo declares (`-e .[dev]` or `-e .`, then requirements.txt / requirements-dev.txt).
145
+ Node: `npm ci` in each of NPM_FOLDERS that has a `package-lock.json`."""
146
+ steps: list[tuple[Path, list[str]]] = []
147
+ pyproject = root / "pyproject.toml"
148
+ reqs = [f for f in ("requirements.txt", "requirements-dev.txt") if (root / f).is_file()]
149
+ if (root / "uv.lock").is_file():
150
+ steps.append((root, ["uv", "sync", "--frozen", "--all-extras"]))
151
+ elif pyproject.is_file() or reqs:
152
+ has_project, has_dev = _declares_dev_extra(pyproject) if pyproject.is_file() else (False, False)
153
+ if has_project or reqs: # a pyproject with only tool config declares nothing to install
154
+ venv = root / ".venv"
155
+ if not venv_python(venv).is_file(): # the folder alone is not enough: an interrupted `venv` leaves it empty
156
+ steps.append((root, [sys.executable, "-m", "venv", ".venv"]))
157
+ py = str(venv_python(venv))
158
+ if has_project:
159
+ steps.append((root, [py, "-m", "pip", "install", "-e", ".[dev]" if has_dev else "."]))
160
+ for f in reqs:
161
+ steps.append((root, [py, "-m", "pip", "install", "-r", f]))
162
+ for folder in NPM_FOLDERS:
163
+ d = root / folder
164
+ if (d / "package-lock.json").is_file():
165
+ steps.append((d, ["npm", "ci"]))
166
+ return steps
167
+
168
+
169
+ def bootstrap(repo: Path | str = ".", run=subprocess.run, which=shutil.which) -> int:
170
+ """Install the dependencies of the linked worktree that contains `repo`. Returns 0, 1 (a step failed or a tool is
171
+ missing) or 2 (not a linked worktree: this never touches a main checkout). `run` and `which` are test seams."""
172
+ repo = Path(repo).absolute()
173
+ top = _git_out(repo, "rev-parse", "--show-toplevel") if repo.is_dir() else None
174
+ if not top:
175
+ print(f"error: {repo} is not inside a git repository", file=sys.stderr)
176
+ return 2
177
+ root = Path(os.path.normpath(top))
178
+ if not is_linked_worktree(root):
179
+ print(f"error: {root} is a main checkout, not a linked worktree. Bootstrap only runs in a worktree "
180
+ "(it would change the checkout's own venv and node_modules).", file=sys.stderr)
181
+ return 2
182
+ steps = plan_bootstrap(root)
183
+ if not steps:
184
+ print(f"bootstrap: nothing to install in {root} (no pyproject.toml, requirements*.txt or package-lock.json)")
185
+ return 0
186
+ for cwd, argv in steps:
187
+ exe = which(argv[0]) if argv[0] in ("uv", "npm") else argv[0]
188
+ if exe is None:
189
+ hint = " (uv.lock needs uv; pip would ignore the lock)" if argv[0] == "uv" else ""
190
+ print(f"error: `{argv[0]}` not found on PATH{hint}", file=sys.stderr)
191
+ return 1
192
+ cmd = [exe, *argv[1:]]
193
+ print(f"bootstrap: ({cwd}) {' '.join(cmd)}", flush=True)
194
+ if run(cmd, cwd=cwd, check=False).returncode != 0:
195
+ print(f"error: step failed: {' '.join(cmd)}", file=sys.stderr)
196
+ return 1
197
+ print(f"bootstrap: done - {root} has its own dependencies")
198
+ return 0
199
+
200
+
99
201
  def main(argv: list[str] | None = None) -> int:
100
202
  ap = argparse.ArgumentParser(description="Print the path for a new git worktree (never under %TEMP%).")
101
- ap.add_argument("short_name", help="one folder name, e.g. fix-login")
203
+ ap.add_argument("short_name", nargs="?", help="one folder name, e.g. fix-login (not used with --bootstrap)")
204
+ ap.add_argument("--bootstrap", action="store_true",
205
+ help="instead of printing a path: install the dependencies of the worktree that contains --repo "
206
+ "(uv sync or venv + pip, and npm ci); exit 2 in a main checkout")
102
207
  ap.add_argument("--repo", default=".", help="any folder of the repo or of one of its worktrees (default: .)")
103
208
  ap.add_argument("--root", default=None, help=f"override the root (default: ${ENV_VAR}, then <repo parent>/.worktrees)")
104
209
  ap.add_argument("--record", action="store_true", help="also record the path in this session's created list")
105
210
  ap.add_argument("--purpose", default="", help="with --record: why the worktree is made")
106
211
  args = ap.parse_args(argv)
212
+ if args.bootstrap:
213
+ return bootstrap(args.repo)
214
+ if not args.short_name:
215
+ ap.error("a short name is required (or use --bootstrap)")
107
216
  try:
108
217
  path = worktree_path(args.repo, args.short_name, args.root)
109
218
  repo = main_checkout(args.repo) if args.record else None
@@ -613,8 +613,14 @@ if __name__ == "__main__":
613
613
  # that is a broken environment, not a project without linting — and a check that cannot
614
614
  # run must not report success. Tools the project never asked for are still skipped
615
615
  # silently, because those genuinely are not part of its standards.
616
+ # Bump when the hook text changes in a way an installed copy should pick up. install_git_hooks replaces a managed hook
617
+ # whose "caddis-pre-push-version" is lower (a hook with no marker counts as 0) and leaves a hook it does not manage alone.
618
+ PRE_PUSH_HOOK_VERSION = 2
619
+ _HOOK_SCRIPTS_PLACEHOLDER = "__CADDIS_SCRIPTS__"
620
+
616
621
  PRE_PUSH_HOOK = r"""#!/usr/bin/env sh
617
622
  # Managed by caddis setup-project-ai. Delete this file to opt out.
623
+ # caddis-pre-push-version: 2
618
624
  set -eu
619
625
  echo "[caddis] pre-push quality gate"
620
626
  fail=0
@@ -626,13 +632,25 @@ else
626
632
  GATE_RUN="./caddis_gate_step.py"
627
633
  fi
628
634
 
629
- # Prefer the project's virtualenv over PATH. Checked in venv-layout order for both
630
- # Windows (Scripts/) and POSIX (bin/) so the same hook works on either.
635
+ # Use the project's own virtualenv, never whatever is on PATH. Both layouts are checked (Windows Scripts/, POSIX bin/).
636
+ # A linked git WORKTREE uses ONLY its own .venv. The main checkout's venv is not an option: it belongs to a running
637
+ # dev service and is often many commits behind the worktree's pins (found 2026-11-03: rbac-kit 0.2.0 against a 0.3.1
638
+ # pin; the old lookup list also held a literal backslash-n typo). Every worktree installs its dependencies fresh.
639
+ HOOK_SCRIPTS_DIR="__CADDIS_SCRIPTS__"
631
640
  PY=""
641
+ IN_WORKTREE=0
642
+ if [ "$(git rev-parse --git-dir 2>/dev/null || echo .git)" != "$(git rev-parse --git-common-dir 2>/dev/null || echo .git)" ]; then
643
+ IN_WORKTREE=1
644
+ fi
632
645
  for cand in .venv/Scripts/python.exe .venv/bin/python venv/Scripts/python.exe venv/bin/python; do
633
646
  if [ -x "$cand" ]; then PY="$cand"; break; fi
634
647
  done
635
- if [ -z "$PY" ]; then PY=$(command -v python || command -v python3 || true); fi
648
+ if [ -z "$PY" ] && [ "$IN_WORKTREE" -eq 0 ]; then
649
+ PY=$(command -v python || command -v python3 || true)
650
+ if [ -n "$PY" ] && { [ -f "pyproject.toml" ] || [ -f "requirements.txt" ]; }; then
651
+ echo "[gate] WARNING: no .venv in this checkout - using the system Python ($PY). Its packages may differ from the project's pins." >&2
652
+ fi
653
+ fi
636
654
 
637
655
  # Runnable IN $PY - not merely present on PATH. This is the whole point: `command -v mypy`
638
656
  # answers a question about PATH, and the question we care about is about the environment
@@ -683,7 +701,16 @@ py_gate() {
683
701
  }
684
702
 
685
703
  if [ -f "pyproject.toml" ] || [ -f "requirements.txt" ]; then
686
- if [ -z "$PY" ]; then
704
+ if [ -z "$PY" ] && [ "$IN_WORKTREE" -eq 1 ]; then
705
+ echo "[gate] this git worktree has no .venv, and the gate will not borrow the main checkout's or the system Python." >&2
706
+ if [ -f "$HOOK_SCRIPTS_DIR/caddis_worktree_root.py" ]; then
707
+ echo " fix, in this worktree: python \"$HOOK_SCRIPTS_DIR/caddis_worktree_root.py\" --bootstrap" >&2
708
+ else
709
+ echo " fix, in this worktree: python \"<caddis scripts>/caddis_worktree_root.py\" --bootstrap (the scripts folder of the installed caddis plugin)" >&2
710
+ fi
711
+ echo "[caddis] push BLOCKED - 'git push --no-verify' overrides." >&2
712
+ exit 1
713
+ elif [ -z "$PY" ]; then
687
714
  echo "[gate] python project, but no interpreter found (.venv or PATH) - cannot verify" >&2
688
715
  fail=1
689
716
  else
@@ -770,8 +797,30 @@ echo "[caddis] gate passed - pushing."
770
797
  """
771
798
 
772
799
 
800
+ _HOOK_MARKER_RE = re.compile(r"Managed by (caddis|claudster)\b")
801
+ _HOOK_VERSION_RE = re.compile(r"^#\s*caddis-pre-push-version:\s*(\d+)", re.MULTILINE)
802
+
803
+
804
+ def render_pre_push_hook() -> str:
805
+ """The hook text to install: the template with this install's scripts folder filled in (forward slashes)."""
806
+ return PRE_PUSH_HOOK.replace(_HOOK_SCRIPTS_PLACEHOLDER, Path(__file__).resolve().parent.as_posix())
807
+
808
+
809
+ def _installed_hook_state(hook_text: str) -> tuple[bool, int]:
810
+ """(managed by caddis, its version). A managed hook with no version marker is version 0. A hook this tool did not
811
+ write is (False, 0): it is never replaced without --force."""
812
+ if not _HOOK_MARKER_RE.search(hook_text): # also recognises pre-rename ("claudster") hooks
813
+ return False, 0
814
+ m = _HOOK_VERSION_RE.search(hook_text)
815
+ return True, int(m.group(1)) if m else 0
816
+
817
+
773
818
  def install_git_hooks(target: Path, force: bool, dry: bool) -> list[str]:
774
- """Install the enforced pre-push quality gate into .git/hooks/pre-push."""
819
+ """Install the enforced pre-push quality gate into .git/hooks/pre-push.
820
+
821
+ An existing caddis-managed hook is replaced when its version is older than PRE_PUSH_HOOK_VERSION and kept when it is
822
+ current. A hook caddis did not write is left alone unless `force`. Git shares `.git/hooks` with every worktree of the
823
+ repo, so one install in the main checkout covers them all."""
775
824
  notes: list[str] = []
776
825
  git = target / ".git"
777
826
  if not git.exists():
@@ -781,13 +830,17 @@ def install_git_hooks(target: Path, force: bool, dry: bool) -> list[str]:
781
830
  hooks_dir = git / "hooks"
782
831
  dest = hooks_dir / "pre-push"
783
832
  step_dest = hooks_dir / "caddis_gate_step.py"
833
+ upgraded_from: int | None = None
784
834
  if dest.exists() and not force:
785
- _hook_txt = dest.read_text(encoding="utf-8", errors="ignore")
786
- managed = "caddis" in _hook_txt or "claudster" in _hook_txt # recognise pre-rename hooks too
787
- return [f"pre-push gate: exists ({'ours' if managed else 'yours — left intact, use --force to replace'}) — skipped"]
835
+ managed, version = _installed_hook_state(dest.read_text(encoding="utf-8", errors="ignore"))
836
+ if not managed:
837
+ return ["pre-push gate: exists (yours — left intact, use --force to replace) — skipped"]
838
+ if version >= PRE_PUSH_HOOK_VERSION:
839
+ return [f"pre-push gate: exists (ours) at version {version}, current — skipped"]
840
+ upgraded_from = version
788
841
  if not dry:
789
842
  hooks_dir.mkdir(parents=True, exist_ok=True)
790
- dest.write_text(PRE_PUSH_HOOK, encoding="utf-8", newline="\n")
843
+ dest.write_text(render_pre_push_hook(), encoding="utf-8", newline="\n")
791
844
  step_dest.write_text(GATE_STEP_PY, encoding="utf-8", newline="\n")
792
845
  try:
793
846
  import stat
@@ -795,7 +848,11 @@ def install_git_hooks(target: Path, force: bool, dry: bool) -> list[str]:
795
848
  step_dest.chmod(step_dest.stat().st_mode | stat.S_IXUSR | stat.S_IXGRP | stat.S_IXOTH)
796
849
  except Exception:
797
850
  pass
798
- notes.append("pre-push gate: installed .git/hooks/pre-push and caddis_gate_step.py (green-before-push enforced)")
851
+ if upgraded_from is not None:
852
+ notes.append(f"pre-push gate: upgraded .git/hooks/pre-push (version {upgraded_from} -> {PRE_PUSH_HOOK_VERSION}) "
853
+ "and caddis_gate_step.py (green-before-push enforced)")
854
+ else:
855
+ notes.append("pre-push gate: installed .git/hooks/pre-push and caddis_gate_step.py (green-before-push enforced)")
799
856
  return notes
800
857
 
801
858
 
@@ -16,7 +16,7 @@
16
16
  | Code Review | `code-review/` | Automated code review for quality, security, performance and best practices. Use when reviewing code changes, PRs, or doing code audits. |
17
17
  | Codebase Audit | `codebase-audit/` | Audit an unfamiliar codebase before architecture or implementation work. Use for a new codebase, pre-implementation audit, codebase review, technical due diligence or onboarding. Produces AUDIT-FINDINGS.md and QUESTIONS.md. |
18
18
  | Cross Review | `cross-review/` | Cross-vendor code review of the current diff — a second-vendor model (agy Argon by default; DeepSeek, GLM or any OpenAI-compatible endpoint) reviews your changes to catch bugs a same-vendor reviewer misses |
19
- | Dashboard Perf Sweep | `dashboard-perf-sweep/` | Re-measure dashboard/API endpoints for load-time regressions and decide by checklist if a slow one needs the rs-kit refresher, an index, keyset paging, gzip, or nothing. Use when the user says "sweep dashboard performance", "check if this app needs rs-kit", "re-measure the perf tracker", "is this endpoint a refresher candidate", or dashboard-performance-tracker.md is stale. Read-only. |
19
+ | Dashboard Perf Sweep | `dashboard-perf-sweep/` | Re-measure dashboard/API endpoints for load-time regressions. Use when the user says "sweep dashboard performance", "check if this app needs rs-kit", or "re-measure the perf tracker". |
20
20
  | Error Handling | `error-handling/` | Error handling for Python and TypeScript: error hierarchies, custom exceptions, result types, retries, circuit breakers, error boundaries, logging, user-facing messages. |
21
21
  | Fastapi Dev | `fastapi-dev/` | Build FastAPI backends with standard patterns, error handling, and testing |
22
22
  | Javascript Typescript | `javascript-typescript/` | JavaScript and TypeScript development with ES6+, Node.js, React, and modern web frameworks. Use for frontend, backend, or full-stack JavaScript/TypeScript projects. |
@@ -30,7 +30,7 @@
30
30
  | Skill | Path | When to Use |
31
31
  |-------|------|-------------|
32
32
  | Database Design | `database-design/` | Database schema design, migrations and query optimization for PostgreSQL, MySQL and NoSQL. |
33
- | Db Diagram | `db-diagram/` | Diagram a SQL artifact (stored proc, view, query, .sql file, table) as Mermaid or Excalidraw. Use when the user says "diagram this query/proc/view/schema", "explain this SQL visually", "draw the ER diagram", "show me the data flow of this stored proc", "/mermaid-db", or "/excalidraw-db". Read-only. |
33
+ | Db Diagram | `db-diagram/` | Diagram SQL artifacts (procs, views, queries, tables) as Mermaid or Excalidraw. Use when the user says "diagram this SQL", "draw the ER diagram", "/mermaid-db", or "/excalidraw-db". |
34
34
 
35
35
  ### Devops
36
36
 
@@ -53,7 +53,7 @@
53
53
  | Code Documentation | `code-documentation/` | Write code documentation: API docs, README files, inline comments and developer guides. |
54
54
  | Confluence Hla | `confluence-hla/` | High-Level Architecture (HLA) documents in Simplified Technical English as Confluence Storage Format XHTML with PlantUML. Use for Confluence architecture docs or converting markdown architecture. |
55
55
  | Data Lineage | `data-lineage/` | Generate End-to-End Data Lineage and Telemetry Specification Markdown and Confluence XHTML for fleet observability. |
56
- | Explainer Doc | `explainer-doc/` | Hand-off doc for a team that did NOT do the investigation (vendor, contractor, another team) — the "stranger must follow it alone" case. Use when the user says "write a spec for the X team", "document this for someone outside the team", "explainer doc", "implementation spec for a vendor", or "hand this off to Y". Not for readers with full context. |
56
+ | Explainer Doc | `explainer-doc/` | Write a self-contained hand-off spec for an external team or vendor. Use when the user says "write a spec for the X team", "explainer doc", "spec for a vendor", or "hand this off to Y". |
57
57
  | Hld | `hld/` | Generate High-Level Design (HLD) Markdown documentation and Confluence XHTML with native PlantUML diagrams. |
58
58
  | Lld | `lld/` | Generate Lower-Level Design (LLD) Markdown documentation and Confluence XHTML with native PlantUML diagrams. |
59
59
  | Office Documents Official | `office-documents-official/` | Hint for Office and PDF file work. Use when the user asks to create, edit, read or convert a Word .docx, PDF, PowerPoint .pptx or Excel .xlsx file. caddis does not ship these skills; points to Anthropic's official document-skills plugin. |
@@ -72,7 +72,7 @@
72
72
  | React Best Practices | `react-best-practices/` | Modern React development guidelines covering hooks, component patterns, state management, performance optimization, and TypeScript integration. |
73
73
  | React Dev | `react-dev/` | Type-safe React 18-19 with TypeScript: components, generic components, hooks, events, Server Components, TanStack Router and React Router. Use when React TypeScript or React 19 is involved. |
74
74
  | Ui Review | `ui-review/` | Review a UI against design requirements, WCAG 2.2 AA and brand guidelines. Use when validating UI before release. |
75
- | Warm Editorial Ui | `warm-editorial-ui/` | Apply the "Warm Editorial Refinement" design system (warm cream/charcoal surfaces, Bahnschrift + Plus Jakarta Sans, layered shadows), the canonical template for new frontend builds. Use for apps, dashboards or UI in the abc-project style, or on "use our design system", "apply our template", "make it look like abc-project", "use the warm editorial style", "use our brand template", "add dark mode", or a new tool for XYZ Brand. |
75
+ | Warm Editorial Ui | `warm-editorial-ui/` | Apply the Warm Editorial Refinement design system. Use when the user says "use our design system", "warm editorial style", "apply our template", or "make it look like abc-project". |
76
76
 
77
77
  ### General
78
78
 
@@ -1,11 +1,8 @@
1
1
  ---
2
2
  name: adopt-app
3
3
  description: >-
4
- Bring an app that was never scaffolded (POC, server folder, checkout with no remote) up to standard:
5
- inventory without running it, pass/gap/question verdicts, ordered plan. Use when the user says "this
6
- app was never set up properly", "adopt this POC", "onboard this app", "it just runs from a folder on
7
- the server", "what would it take to get this into CI", "nobody knows how this is deployed", or "it
8
- started as a prototype and now it is production".
4
+ Inventory an unscaffolded app or POC read-only and produce an adoption plan. Use when the user
5
+ says "adopt this POC", "onboard this app", "never set up properly", or "get this into CI".
9
6
  ---
10
7
 
11
8
  # adopt-app
@@ -41,7 +41,7 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
41
41
  `git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
42
42
  - **Pull a branch to test it:** `git fetch origin`, then
43
43
  `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
44
- `origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
44
+ `origin/<default>`), and run the gates there. Install dependencies fresh with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" --bootstrap` (run in the worktree); never link `node_modules` or a venv.
45
45
  - **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
46
46
  `git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
47
47
  checkout has the default branch out; then leave it and report it. Delete the local feature branch only when no
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: dashboard-perf-sweep
3
3
  context: fork
4
- description: Re-measure dashboard/API endpoints for load-time regressions and decide by checklist if a slow one needs the rs-kit refresher, an index, keyset paging, gzip, or nothing. Use when the user says "sweep dashboard performance", "check if this app needs rs-kit", "re-measure the perf tracker", "is this endpoint a refresher candidate", or dashboard-performance-tracker.md is stale. Read-only.
4
+ description: Re-measure dashboard/API endpoints for load-time regressions. Use when the user says "sweep dashboard performance", "check if this app needs rs-kit", or "re-measure the perf tracker".
5
5
  ---
6
6
 
7
7
  # dashboard-perf-sweep — re-measure, then judge the shape, not just the time
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: db-diagram
3
3
  context: fork
4
- description: Diagram a SQL artifact (stored proc, view, query, .sql file, table) as Mermaid or Excalidraw. Use when the user says "diagram this query/proc/view/schema", "explain this SQL visually", "draw the ER diagram", "show me the data flow of this stored proc", "/mermaid-db", or "/excalidraw-db". Read-only.
4
+ description: Diagram SQL artifacts (procs, views, queries, tables) as Mermaid or Excalidraw. Use when the user says "diagram this SQL", "draw the ER diagram", "/mermaid-db", or "/excalidraw-db".
5
5
  ---
6
6
 
7
7
  # db-diagram — explain SQL as a diagram
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: explainer-doc
3
3
  context: fork
4
- description: Hand-off doc for a team that did NOT do the investigation (vendor, contractor, another team) — the "stranger must follow it alone" case. Use when the user says "write a spec for the X team", "document this for someone outside the team", "explainer doc", "implementation spec for a vendor", or "hand this off to Y". Not for readers with full context.
4
+ description: Write a self-contained hand-off spec for an external team or vendor. Use when the user says "write a spec for the X team", "explainer doc", "spec for a vendor", or "hand this off to Y".
5
5
  ---
6
6
 
7
7
  # explainer-doc — write for the reader who has no other context
@@ -91,6 +91,10 @@ and 95-154 turns per session were started by background events. Each turn re-rea
91
91
  `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_spend.py" run --caller lane-pN -- agy ...`.
92
92
  - **Fewer wake-ups.** Run one `ci-watch` per PR head. When it times out on a queued run, watch that run once
93
93
  with `ci-watch --run <id>`; do not start a new PR watch. Write no "still waiting" turns.
94
+ - **Silent agents.** For a subagent in its own worktree, start the shell watcher in the background (a script, not a
95
+ model): `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_silence_watch.py" --worktree <path> --silent-min 20`. Exit 3
96
+ and a `SILENT:` line mean no commit, file change or output for 20 minutes. Then look at the agent, and stop or
97
+ resume it. Add `--extra-file <the agent's output file>` so a long quiet build does not count as silence.
94
98
 
95
99
  ## Waves
96
100
 
@@ -1,11 +1,8 @@
1
1
  ---
2
2
  name: port-to-github
3
3
  description: >-
4
- Port an app or repo to GitHub from any source (git server, local folder, UNC share, Windows box over
5
- WinRM): all branches and tags, SHA-verified, CI translated, source-only history, deploy cut over
6
- with rollback. Use when the user says "move this app to GitHub", "port X to GitHub", "migrate from
7
- Gitea", "this app only exists on the server", "import the repo from the prod box", "keep binaries
8
- out of the repo", or "cut the deploy over to GitHub".
4
+ Port an app or repo to GitHub with verified history, CI translation, and deploy cutover. Use when
5
+ the user says "move this app to GitHub", "port X to GitHub", or "migrate from Gitea".
9
6
  ---
10
7
 
11
8
  # port-to-github
@@ -47,7 +47,7 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
47
47
  `git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
48
48
  - **Pull a branch to test it:** `git fetch origin`, then
49
49
  `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
50
- `origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
50
+ `origin/<default>`), and run the gates there. Install dependencies fresh with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" --bootstrap` (run in the worktree); never link `node_modules` or a venv.
51
51
  - **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
52
52
  `git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
53
53
  checkout has the default branch out; then leave it and report it. Delete the local feature branch only when no
@@ -46,7 +46,7 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
46
46
  `git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
47
47
  - **Pull a branch to test it:** `git fetch origin`, then
48
48
  `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
49
- `origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
49
+ `origin/<default>`), and run the gates there. Install dependencies fresh with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" --bootstrap` (run in the worktree); never link `node_modules` or a venv.
50
50
  - **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
51
51
  `git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
52
52
  checkout has the default branch out; then leave it and report it. Delete the local feature branch only when no
@@ -45,7 +45,7 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
45
45
  `git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
46
46
  - **Pull a branch to test it:** `git fetch origin`, then
47
47
  `git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
48
- `origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
48
+ `origin/<default>`), and run the gates there. Install dependencies fresh with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" --bootstrap` (run in the worktree); never link `node_modules` or a venv.
49
49
  - **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
50
50
  `git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
51
51
  checkout has the default branch out; then leave it and report it. Delete the local feature branch only when no
@@ -2,12 +2,8 @@
2
2
  name: tech-explainer
3
3
  context: fork
4
4
  description: >-
5
- Plain-language explainer, with ranked Mermaid diagrams and Simplified Technical English, for a
6
- reader who did NOT do the investigation (manager, stakeholder). Use when the user says "explain this
7
- to X", "explainer", "write this up for someone non-technical", "plain English", "STE", "explain our
8
- findings", "write up the benchmark results", "why is it slow — document it", or summarises an
9
- investigation for a reader who won't read the raw data. Not for build hand-offs (explainer-doc) or
10
- READMEs.
5
+ Plain-language explainer with Mermaid diagrams and STE for stakeholders. Use when the user says
6
+ "explain this to X", "plain English", "STE", or "explain our findings".
11
7
  ---
12
8
 
13
9
  # tech-explainer — make a stranger understand, and able to push back
@@ -55,8 +55,25 @@ git worktree add -b <branch> $wt origin/<default>
55
55
 
56
56
  ## Install dependencies fresh
57
57
 
58
- Install inside the worktree. Use the project's own command (`npm ci`, `python -m venv .venv` then
59
- `.venv\Scripts\python -m pip install -r requirements.txt`, `cargo build`, `go mod download`). Call the
58
+ Run one command, inside the new worktree:
59
+
60
+ ```powershell
61
+ python "<caddis scripts>\caddis_worktree_root.py" --bootstrap
62
+ ```
63
+
64
+ It installs this worktree's own dependencies:
65
+
66
+ - `uv sync --frozen --all-extras` when `uv.lock` exists. Without `uv.lock`: `python -m venv .venv`, then `pip install`
67
+ of what the repo declares (`-e ".[dev]"` or `-e .`, then `requirements.txt` and `requirements-dev.txt`).
68
+ - `npm ci` in the root and in `frontend/`, for each folder that has a `package-lock.json`.
69
+
70
+ It refuses to run in a main checkout (exit 2) and stops at the first failing step (exit 1).
71
+
72
+ The pre-push gate needs this. In a worktree the gate uses only the worktree's own `.venv`. It never uses the main
73
+ checkout's venv (stale, and it belongs to a running dev service) and never the system Python. A worktree with no
74
+ `.venv` fails the gate with this command in the message. Do not push with `--no-verify` to get round it.
75
+
76
+ For a stack the script does not cover, use the project's own command (`cargo build`, `go mod download`). Call the
60
77
  venv's own `python`; a bare `pip` can install into the global Python.
61
78
 
62
79
  Never link `node_modules` or a venv from another folder. Tools that follow the link then change the
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: warm-editorial-ui
3
- description: Apply the "Warm Editorial Refinement" design system (warm cream/charcoal surfaces, Bahnschrift + Plus Jakarta Sans, layered shadows), the canonical template for new frontend builds. Use for apps, dashboards or UI in the abc-project style, or on "use our design system", "apply our template", "make it look like abc-project", "use the warm editorial style", "use our brand template", "add dark mode", or a new tool for XYZ Brand.
3
+ description: Apply the Warm Editorial Refinement design system. Use when the user says "use our design system", "warm editorial style", "apply our template", or "make it look like abc-project".
4
4
  ---
5
5
 
6
6
  # Warm Editorial Refinement — Design System
@@ -1,5 +1,5 @@
1
1
  {
2
2
  "name": "caddis-extras",
3
- "version": "1.3.50",
3
+ "version": "1.3.51",
4
4
  "description": "caddis-extras — the long-tail skills for the Antigravity (agy) caddis plugin; install alongside caddis for the full set."
5
5
  }
@@ -131,12 +131,12 @@
131
131
  | Agent Md Refactor | `agent-md-refactor/` | Refactor bloated agent instruction files (AGENTS.md, .cursorrules, .github/ files) into linked, progressively disclosed docs. |
132
132
  | Agent Orchestration | `agent-orchestration/` | Blueprint for orchestrating the agent pipeline from spec to planning, implementation, testing and debugging, plus when a second model is worth it, the intent→model map and cost guardrails. |
133
133
  | Ask Questions If Underspecified | `asking-questions/` | Clarify requirements before implementing. Do not use automatically, only when invoked explicitly. |
134
- | Data Contract Pipeline | `data-contract-pipeline/` | Build, audit and validate data-to-UI contracts. Use when the user mentions data mapping, UI lineage, DB-to-UI, DisplayDTOs, source-to-screen mapping, data contracts, schema drift, typed API responses, mockup grounding, or asks whether a UI is backed by real data. |
134
+ | Data Contract Pipeline | `data-contract-pipeline/` | Build, audit, and validate DB-to-UI data contracts. Use when the user mentions data mapping, UI lineage, DisplayDTOs, source-to-screen mapping, or asks if a UI is backed by real data. |
135
135
  | Developer Growth Analysis | `developer-growth-analysis/` | Analyze recent Claude Code chat history for coding patterns and gaps, find learning resources on HackerNews, and send a growth report to Slack DMs. |
136
136
  | File Organizer | `file-organizer/` | Organize files and folders by context: find duplicates, suggest better structures, automate cleanup. |
137
137
  | Game Changing Features | `game-changing-features/` | Find 10x product opportunities and high-leverage features. Use when the user mentions '10x', says 'what would make this 10x better', 'product strategy', or 'what should we build next'. |
138
138
  | Golden Nuggets | `golden-nuggets/` | Extract durable tribal knowledge ('gold nuggets') from a codebase or changed files and route each to an instruction file, runbook, hub or CI review inbox. Use after a feature, fix, sprint, incident or release. |
139
139
  | Intent Writer | `intent-writer/` | Structure freetext ideas, backlog items, or vague requirements into a formal Intent Document that preserves user intent across the entire agent pipeline chain. |
140
140
  | Receiving Code Review | `receiving-code-review/` | Use when receiving code review feedback, before implementing it, especially if it seems unclear or wrong: verify with technical rigor, no performative agreement or blind implementation. |
141
- | Setup Project Ai | `setup-project-ai/` | Install or refresh the agent-agnostic harness in a project: AGENTS.md rules with CLAUDE.md shims, subagents, commands and settings. Use when setting up AI resources on a project, or the user says 'set up the harness', 'setup-project-ai', 'generate CLAUDE.md', 'onboard this project to Claude Code / Codex / agy', or runs /setup-project-ai. |
141
+ | Setup Project Ai | `setup-project-ai/` | Install or refresh the project AI harness: AGENTS.md, CLAUDE.md shims, agents, settings. Use when the user says 'set up the harness', 'generate CLAUDE.md', or runs /setup-project-ai. |
142
142
  | Verification Loop | `verification-loop/` | Systematic code change verification — lint, test, type-check, review |
@@ -3,8 +3,7 @@ name: building-ai-agent-on-cloudflare
3
3
  context: fork
4
4
  description: |
5
5
  Builds stateful AI agents on Cloudflare Workers with the Agents SDK. Use when the user wants to
6
- "build an agent", "AI agent", "chat agent", "stateful agent", mentions "Agents SDK", "real-time
7
- AI", "WebSocket AI", or asks about agent "state management", "scheduled tasks" or "tool calling".
6
+ "build an agent", "stateful agent", "WebSocket AI", or mentions "Agents SDK".
8
7
  ---
9
8
 
10
9
  # Building Cloudflare Agents
@@ -3,8 +3,7 @@ name: building-mcp-server-on-cloudflare
3
3
  context: fork
4
4
  description: |
5
5
  Builds and deploys remote MCP servers on Cloudflare Workers with tools and OAuth. Use when the
6
- user wants to "build MCP server", "create MCP tools", "remote MCP", "deploy MCP", add "OAuth to
7
- MCP", or mentions "MCP authentication", "MCP deployment" or Model Context Protocol on Cloudflare.
6
+ user wants to "build MCP server", "remote MCP", "deploy MCP", or add "OAuth to MCP".
8
7
  ---
9
8
 
10
9
  # Building MCP Servers on Cloudflare
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: data-contract-pipeline
3
3
  context: fork
4
- description: "Build, audit and validate data-to-UI contracts. Use when the user mentions data mapping, UI lineage, DB-to-UI, DisplayDTOs, source-to-screen mapping, data contracts, schema drift, typed API responses, mockup grounding, or asks whether a UI is backed by real data."
4
+ description: "Build, audit, and validate DB-to-UI data contracts. Use when the user mentions data mapping, UI lineage, DisplayDTOs, source-to-screen mapping, or asks if a UI is backed by real data."
5
5
  ---
6
6
 
7
7
  # Data Contract Pipeline
@@ -1,10 +1,8 @@
1
1
  ---
2
2
  name: responsive-mobile-native
3
3
  description: >
4
- Make a web app work and "feel native" on phones and tablets from one codebase: adapt desktop-first
5
- layouts, fix small-screen breakage. Use for "make this PWA", "mobile-friendly", "tablet layout",
6
- "bottom nav", "touch gestures", "works on iPhone/Android", "responsive design", or any web UI
7
- missing mobile support.
4
+ Adapt desktop-first web apps into responsive, mobile-native PWAs from one codebase. Use when the
5
+ user says "make this PWA", "mobile-friendly", "tablet layout", or "responsive design".
8
6
  ---
9
7
 
10
8
  # Responsive Mobile-Native Skill
@@ -1,10 +1,8 @@
1
1
  ---
2
2
  name: runner-move
3
3
  description: >-
4
- Move GitHub Actions jobs from self-hosted runners to GitHub-hosted runners, one repo at a time,
5
- with a cost check and a pilot PR. Use when the user says "move CI to GitHub-hosted runners",
6
- "stop using self-hosted runners", "runner migration", "move jobs off the runner box", or "run
7
- CI on windows-latest or ubuntu-latest".
4
+ Move GitHub Actions jobs from self-hosted to GitHub-hosted runners. Use when the user says
5
+ "move CI to GitHub-hosted runners", "stop using self-hosted runners", or "runner migration".
8
6
  ---
9
7
 
10
8
  # runner-move
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: setup-project-ai
3
- description: "Install or refresh the agent-agnostic harness in a project: AGENTS.md rules with CLAUDE.md shims, subagents, commands and settings. Use when setting up AI resources on a project, or the user says 'set up the harness', 'setup-project-ai', 'generate CLAUDE.md', 'onboard this project to Claude Code / Codex / agy', or runs /setup-project-ai."
3
+ description: "Install or refresh the project AI harness: AGENTS.md, CLAUDE.md shims, agents, settings. Use when the user says 'set up the harness', 'generate CLAUDE.md', or runs /setup-project-ai."
4
4
  ---
5
5
 
6
6
  # setup-project-ai
@@ -1,11 +1,8 @@
1
1
  ---
2
2
  name: understand-anything
3
3
  description: >
4
- Turn a codebase or knowledge base into a searchable interactive knowledge graph. Use for
5
- /understand and /understand-chat, -dashboard, -diff, -domain, -explain, -knowledge, -onboard, or
6
- phrases like "how does this project work", "map out the codebase", "what changed in this PR",
7
- "explain this file", "onboard me to this project", "what does X depend on", "analyze this repo",
8
- "generate a knowledge graph", or "what is the architecture of this project".
4
+ Turn a codebase into an interactive knowledge graph. Use for /understand* commands, or when the
5
+ user says "map out the codebase", "how does this project work", or "knowledge graph".
9
6
  ---
10
7
 
11
8
  # Understand Anything