From eb447dad2e9beeff013a34fd8dcce35a0eca9da1 Mon Sep 17 00:00:00 2001 From: Julius Brussee Date: Fri, 12 Jun 2026 14:12:04 +0200 Subject: [PATCH] chore: remove stale dotdir cavecrew mirrors MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit .junie/, .kiro/, .roo/, .agents/ held pre-cleanup cavecrew/SKILL.md mirrors (plus an unused .agents/plugins/marketplace.json). Nothing in the current install path reads them — bin/install.js handles Codex via npx skills add, and Claude Code marketplace discovery uses .claude-plugin/marketplace.json. CLAUDE.md marks these remove-on-sight. Co-Authored-By: Claude Opus 4.8 (1M context) --- .agents/plugins/marketplace.json | 20 -------- .agents/skills/cavecrew/SKILL.md | 82 -------------------------------- .junie/skills/cavecrew/SKILL.md | 82 -------------------------------- .kiro/skills/cavecrew/SKILL.md | 82 -------------------------------- .roo/skills/cavecrew/SKILL.md | 82 -------------------------------- 5 files changed, 348 deletions(-) delete mode 100644 .agents/plugins/marketplace.json delete mode 100644 .agents/skills/cavecrew/SKILL.md delete mode 100644 .junie/skills/cavecrew/SKILL.md delete mode 100644 .kiro/skills/cavecrew/SKILL.md delete mode 100644 .roo/skills/cavecrew/SKILL.md diff --git a/.agents/plugins/marketplace.json b/.agents/plugins/marketplace.json deleted file mode 100644 index 173d25a..0000000 --- a/.agents/plugins/marketplace.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "name": "caveman-repo", - "interface": { - "displayName": "Caveman Repo" - }, - "plugins": [ - { - "name": "caveman", - "source": { - "source": "local", - "path": "./plugins/caveman" - }, - "policy": { - "installation": "AVAILABLE", - "authentication": "ON_INSTALL" - }, - "category": "Productivity" - } - ] -} diff --git a/.agents/skills/cavecrew/SKILL.md b/.agents/skills/cavecrew/SKILL.md deleted file mode 100644 index efa413f..0000000 --- a/.agents/skills/cavecrew/SKILL.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -name: cavecrew -description: > - Decision guide for delegating to caveman-style subagents. Tells the main - thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` - (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the - work inline or using vanilla `Explore`. Subagent output is caveman-compressed - so the tool-result injected back into main context is ~60% smaller — main - context lasts longer across long sessions. - Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", - "save context", "compressed agent output". ---- - -Cavecrew = three subagent presets that emit caveman output. Same job as Anthropic defaults (`Explore`, edit-style agents, reviewer); difference is the tool-result they return is compressed, so main context shrinks per delegation. - -## When to use cavecrew vs alternatives - -| Task | Use | -|---|---| -| "Where is X defined / what calls Y / list uses of Z" | `cavecrew-investigator` | -| Same but you also want suggestions/architecture commentary | `Explore` (vanilla) | -| Surgical edit, ≤2 files, scope obvious | `cavecrew-builder` | -| New feature / 3+ files / cross-cutting refactor | Main thread or `feature-dev:code-architect` | -| Review diff, branch, or file for bugs | `cavecrew-reviewer` | -| Deep code review with rationale + alternatives | `Code Reviewer` (vanilla) | -| One-line answer you already know | Main thread, no subagent | - -Rule of thumb: **if you'd want the subagent's output in 1/3 the tokens, pick cavecrew. If you'd want prose, pick vanilla.** - -## Why this exists (the real win) - -Subagent tool results get injected into main context verbatim. A vanilla `Explore` that returns 2k tokens of prose costs 2k tokens of main-context budget every time. The same finding from `cavecrew-investigator` returns ~700 tokens. Across 20 delegations in one session that's the difference between context exhaustion and finishing the task. - -## Output contracts - -What main thread can rely on per agent: - -**`cavecrew-investigator`** -``` -
: -- path:line — `symbol` — short note -totals: . -``` -Or `No match.` Always file-path-first, line-number-attached, backticked symbols. Safe to grep with `path:\d+`. - -**`cavecrew-builder`** -``` - — . -verified: . -``` -Or one of: `too-big.` / `needs-confirm.` / `ambiguous.` / `regressed.` (terminal first token). - -**`cavecrew-reviewer`** -``` -path:line: : . . -totals: N🔴 N🟡 N🔵 N❓ -``` -Or `No issues.` Findings sorted file → line ascending. - -## Chaining patterns - -**Locate → fix → verify** (most common): -1. `cavecrew-investigator` returns site list. -2. Main thread picks 1-2 sites, hands paths to `cavecrew-builder`. -3. `cavecrew-reviewer` audits the diff. - -**Parallel scout** (when investigation is broad): -Spawn 2-3 `cavecrew-investigator` calls in one message (different angles: defs vs callers vs tests). Aggregate in main thread. - -**Single-shot edit** (when site is already known): -Skip investigator. Hand exact path:line to `cavecrew-builder` directly. - -## What NOT to do - -- Don't use `cavecrew-builder` when you don't already know the file. Spawn investigator first or main thread will eat tokens passing context. -- Don't chain `cavecrew-investigator → cavecrew-builder` for a 5-file refactor. Builder will return `too-big.` and you'll have wasted a turn. -- Don't ask `cavecrew-reviewer` for "general feedback" — it returns findings only, no architecture opinions. Use `Code Reviewer` for that. -- Don't expect prose. Cavecrew output is structured, sometimes terse to the point of cryptic. If a human will read it directly, paraphrase. - -## Auto-clarity (inherited) - -Subagents drop caveman → normal English for security warnings, irreversible-action confirmations, and any output where fragment ambiguity could be misread. Resume caveman after. diff --git a/.junie/skills/cavecrew/SKILL.md b/.junie/skills/cavecrew/SKILL.md deleted file mode 100644 index efa413f..0000000 --- a/.junie/skills/cavecrew/SKILL.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -name: cavecrew -description: > - Decision guide for delegating to caveman-style subagents. Tells the main - thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` - (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the - work inline or using vanilla `Explore`. Subagent output is caveman-compressed - so the tool-result injected back into main context is ~60% smaller — main - context lasts longer across long sessions. - Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", - "save context", "compressed agent output". ---- - -Cavecrew = three subagent presets that emit caveman output. Same job as Anthropic defaults (`Explore`, edit-style agents, reviewer); difference is the tool-result they return is compressed, so main context shrinks per delegation. - -## When to use cavecrew vs alternatives - -| Task | Use | -|---|---| -| "Where is X defined / what calls Y / list uses of Z" | `cavecrew-investigator` | -| Same but you also want suggestions/architecture commentary | `Explore` (vanilla) | -| Surgical edit, ≤2 files, scope obvious | `cavecrew-builder` | -| New feature / 3+ files / cross-cutting refactor | Main thread or `feature-dev:code-architect` | -| Review diff, branch, or file for bugs | `cavecrew-reviewer` | -| Deep code review with rationale + alternatives | `Code Reviewer` (vanilla) | -| One-line answer you already know | Main thread, no subagent | - -Rule of thumb: **if you'd want the subagent's output in 1/3 the tokens, pick cavecrew. If you'd want prose, pick vanilla.** - -## Why this exists (the real win) - -Subagent tool results get injected into main context verbatim. A vanilla `Explore` that returns 2k tokens of prose costs 2k tokens of main-context budget every time. The same finding from `cavecrew-investigator` returns ~700 tokens. Across 20 delegations in one session that's the difference between context exhaustion and finishing the task. - -## Output contracts - -What main thread can rely on per agent: - -**`cavecrew-investigator`** -``` -
: -- path:line — `symbol` — short note -totals: . -``` -Or `No match.` Always file-path-first, line-number-attached, backticked symbols. Safe to grep with `path:\d+`. - -**`cavecrew-builder`** -``` - — . -verified: . -``` -Or one of: `too-big.` / `needs-confirm.` / `ambiguous.` / `regressed.` (terminal first token). - -**`cavecrew-reviewer`** -``` -path:line: : . . -totals: N🔴 N🟡 N🔵 N❓ -``` -Or `No issues.` Findings sorted file → line ascending. - -## Chaining patterns - -**Locate → fix → verify** (most common): -1. `cavecrew-investigator` returns site list. -2. Main thread picks 1-2 sites, hands paths to `cavecrew-builder`. -3. `cavecrew-reviewer` audits the diff. - -**Parallel scout** (when investigation is broad): -Spawn 2-3 `cavecrew-investigator` calls in one message (different angles: defs vs callers vs tests). Aggregate in main thread. - -**Single-shot edit** (when site is already known): -Skip investigator. Hand exact path:line to `cavecrew-builder` directly. - -## What NOT to do - -- Don't use `cavecrew-builder` when you don't already know the file. Spawn investigator first or main thread will eat tokens passing context. -- Don't chain `cavecrew-investigator → cavecrew-builder` for a 5-file refactor. Builder will return `too-big.` and you'll have wasted a turn. -- Don't ask `cavecrew-reviewer` for "general feedback" — it returns findings only, no architecture opinions. Use `Code Reviewer` for that. -- Don't expect prose. Cavecrew output is structured, sometimes terse to the point of cryptic. If a human will read it directly, paraphrase. - -## Auto-clarity (inherited) - -Subagents drop caveman → normal English for security warnings, irreversible-action confirmations, and any output where fragment ambiguity could be misread. Resume caveman after. diff --git a/.kiro/skills/cavecrew/SKILL.md b/.kiro/skills/cavecrew/SKILL.md deleted file mode 100644 index efa413f..0000000 --- a/.kiro/skills/cavecrew/SKILL.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -name: cavecrew -description: > - Decision guide for delegating to caveman-style subagents. Tells the main - thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` - (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the - work inline or using vanilla `Explore`. Subagent output is caveman-compressed - so the tool-result injected back into main context is ~60% smaller — main - context lasts longer across long sessions. - Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", - "save context", "compressed agent output". ---- - -Cavecrew = three subagent presets that emit caveman output. Same job as Anthropic defaults (`Explore`, edit-style agents, reviewer); difference is the tool-result they return is compressed, so main context shrinks per delegation. - -## When to use cavecrew vs alternatives - -| Task | Use | -|---|---| -| "Where is X defined / what calls Y / list uses of Z" | `cavecrew-investigator` | -| Same but you also want suggestions/architecture commentary | `Explore` (vanilla) | -| Surgical edit, ≤2 files, scope obvious | `cavecrew-builder` | -| New feature / 3+ files / cross-cutting refactor | Main thread or `feature-dev:code-architect` | -| Review diff, branch, or file for bugs | `cavecrew-reviewer` | -| Deep code review with rationale + alternatives | `Code Reviewer` (vanilla) | -| One-line answer you already know | Main thread, no subagent | - -Rule of thumb: **if you'd want the subagent's output in 1/3 the tokens, pick cavecrew. If you'd want prose, pick vanilla.** - -## Why this exists (the real win) - -Subagent tool results get injected into main context verbatim. A vanilla `Explore` that returns 2k tokens of prose costs 2k tokens of main-context budget every time. The same finding from `cavecrew-investigator` returns ~700 tokens. Across 20 delegations in one session that's the difference between context exhaustion and finishing the task. - -## Output contracts - -What main thread can rely on per agent: - -**`cavecrew-investigator`** -``` -
: -- path:line — `symbol` — short note -totals: . -``` -Or `No match.` Always file-path-first, line-number-attached, backticked symbols. Safe to grep with `path:\d+`. - -**`cavecrew-builder`** -``` - — . -verified: . -``` -Or one of: `too-big.` / `needs-confirm.` / `ambiguous.` / `regressed.` (terminal first token). - -**`cavecrew-reviewer`** -``` -path:line: : . . -totals: N🔴 N🟡 N🔵 N❓ -``` -Or `No issues.` Findings sorted file → line ascending. - -## Chaining patterns - -**Locate → fix → verify** (most common): -1. `cavecrew-investigator` returns site list. -2. Main thread picks 1-2 sites, hands paths to `cavecrew-builder`. -3. `cavecrew-reviewer` audits the diff. - -**Parallel scout** (when investigation is broad): -Spawn 2-3 `cavecrew-investigator` calls in one message (different angles: defs vs callers vs tests). Aggregate in main thread. - -**Single-shot edit** (when site is already known): -Skip investigator. Hand exact path:line to `cavecrew-builder` directly. - -## What NOT to do - -- Don't use `cavecrew-builder` when you don't already know the file. Spawn investigator first or main thread will eat tokens passing context. -- Don't chain `cavecrew-investigator → cavecrew-builder` for a 5-file refactor. Builder will return `too-big.` and you'll have wasted a turn. -- Don't ask `cavecrew-reviewer` for "general feedback" — it returns findings only, no architecture opinions. Use `Code Reviewer` for that. -- Don't expect prose. Cavecrew output is structured, sometimes terse to the point of cryptic. If a human will read it directly, paraphrase. - -## Auto-clarity (inherited) - -Subagents drop caveman → normal English for security warnings, irreversible-action confirmations, and any output where fragment ambiguity could be misread. Resume caveman after. diff --git a/.roo/skills/cavecrew/SKILL.md b/.roo/skills/cavecrew/SKILL.md deleted file mode 100644 index efa413f..0000000 --- a/.roo/skills/cavecrew/SKILL.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -name: cavecrew -description: > - Decision guide for delegating to caveman-style subagents. Tells the main - thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` - (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the - work inline or using vanilla `Explore`. Subagent output is caveman-compressed - so the tool-result injected back into main context is ~60% smaller — main - context lasts longer across long sessions. - Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", - "save context", "compressed agent output". ---- - -Cavecrew = three subagent presets that emit caveman output. Same job as Anthropic defaults (`Explore`, edit-style agents, reviewer); difference is the tool-result they return is compressed, so main context shrinks per delegation. - -## When to use cavecrew vs alternatives - -| Task | Use | -|---|---| -| "Where is X defined / what calls Y / list uses of Z" | `cavecrew-investigator` | -| Same but you also want suggestions/architecture commentary | `Explore` (vanilla) | -| Surgical edit, ≤2 files, scope obvious | `cavecrew-builder` | -| New feature / 3+ files / cross-cutting refactor | Main thread or `feature-dev:code-architect` | -| Review diff, branch, or file for bugs | `cavecrew-reviewer` | -| Deep code review with rationale + alternatives | `Code Reviewer` (vanilla) | -| One-line answer you already know | Main thread, no subagent | - -Rule of thumb: **if you'd want the subagent's output in 1/3 the tokens, pick cavecrew. If you'd want prose, pick vanilla.** - -## Why this exists (the real win) - -Subagent tool results get injected into main context verbatim. A vanilla `Explore` that returns 2k tokens of prose costs 2k tokens of main-context budget every time. The same finding from `cavecrew-investigator` returns ~700 tokens. Across 20 delegations in one session that's the difference between context exhaustion and finishing the task. - -## Output contracts - -What main thread can rely on per agent: - -**`cavecrew-investigator`** -``` -
: -- path:line — `symbol` — short note -totals: . -``` -Or `No match.` Always file-path-first, line-number-attached, backticked symbols. Safe to grep with `path:\d+`. - -**`cavecrew-builder`** -``` - — . -verified: . -``` -Or one of: `too-big.` / `needs-confirm.` / `ambiguous.` / `regressed.` (terminal first token). - -**`cavecrew-reviewer`** -``` -path:line: : . . -totals: N🔴 N🟡 N🔵 N❓ -``` -Or `No issues.` Findings sorted file → line ascending. - -## Chaining patterns - -**Locate → fix → verify** (most common): -1. `cavecrew-investigator` returns site list. -2. Main thread picks 1-2 sites, hands paths to `cavecrew-builder`. -3. `cavecrew-reviewer` audits the diff. - -**Parallel scout** (when investigation is broad): -Spawn 2-3 `cavecrew-investigator` calls in one message (different angles: defs vs callers vs tests). Aggregate in main thread. - -**Single-shot edit** (when site is already known): -Skip investigator. Hand exact path:line to `cavecrew-builder` directly. - -## What NOT to do - -- Don't use `cavecrew-builder` when you don't already know the file. Spawn investigator first or main thread will eat tokens passing context. -- Don't chain `cavecrew-investigator → cavecrew-builder` for a 5-file refactor. Builder will return `too-big.` and you'll have wasted a turn. -- Don't ask `cavecrew-reviewer` for "general feedback" — it returns findings only, no architecture opinions. Use `Code Reviewer` for that. -- Don't expect prose. Cavecrew output is structured, sometimes terse to the point of cryptic. If a human will read it directly, paraphrase. - -## Auto-clarity (inherited) - -Subagents drop caveman → normal English for security warnings, irreversible-action confirmations, and any output where fragment ambiguity could be misread. Resume caveman after.