feat(plugins/cix): bundle cix-workspace skill + investigator sub-agent (v0.2.0)#40
Merged
Merged
Conversation
…t (v0.2.0) When users install the cix plugin via the Claude Code marketplace they should get the cross-project research workflow + the read-only investigator sub-agent automatically — without separate `cp -r` of top-level `skills/` and `~/.claude/agents/` files. This commit moves both artifacts into the plugin tree so marketplace install picks them up in one step. Plugin additions: - `plugins/cix/skills/cix-workspace/SKILL.md` — workflow skill (10 trust rules, four-part fan-out prompt template, anti-patterns, worked example). - `plugins/cix/agents/cix-workspace-investigator.md` — read-only sub-agent. Tools: Bash + Read + Grep. Hard rules baked in (one repo per spawn, no edits, no recursion). - `plugins/cix/tests/workspace-bundle.bats` — 10 regression tests: files present, frontmatter parses, manual-only enforced (no `when_to_use:` block), sub-agent tools list is read-only, manifest version >= 0.2.0. Manual-only by design: - The cix-workspace skill does NOT auto-trigger. Frontmatter has no `when_to_use:` heuristic block; `description:` explicitly says "Do not auto-trigger". Invocation is exclusively via `/cix-workspace <task>`. - Rationale: the workspace flow is heavier than single-repo `cix search` (multi-repo fan-out, sub-agent spawns). Auto-trigger on every prompt that vaguely mentions "services" would burn context for no reason. Load it deliberately. Policy may relax once "is-this-really-cross-project?" heuristics are more reliable. - A bats test (`workspace-bundle.bats`) pins this — re-adding `when_to_use:` fails CI. Plugin manifest bumped 0.1.0 → 0.2.0: - Description updated to mention the workspace skill + sub-agent. - Keywords expanded with workspace / cross-project / monorepo / sub-agent. - marketplace.json description mirrors plugin.json. Top-level docs aligned: - `workspaces.md`, `README.md`, `skills/README.md`: install instructions now lead with the marketplace plugin install; manual `cp -r` kept as the "legacy" path. All three call out that the skill is manual-only. - `skills/cix-workspace/SKILL.md` (top-level copy) mirrors the plugin's frontmatter for consistency. Tests: full 70/70 bats suite passes locally (60 existing + 10 new workspace-bundle assertions). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bundles the cross-project research workflow into the
cixClaude Codeplugin so marketplace install delivers everything in one step — no
separate manual
cp -rofskills/cix-workspace/and~/.claude/agents/files.Bumps the plugin v0.1.0 → v0.2.0 (minor: new functionality, no
breaking changes to the existing single-repo
cixskill or hooks).What's bundled
plugins/cix/skills/cix-workspace/SKILL.md— cross-projectworkflow skill: ten trust rules for
projects[]/chunks[],four-part fan-out prompt template, anti-patterns list, worked
example.
plugins/cix/agents/cix-workspace-investigator.md— read-onlysub-agent for parallel per-repo deep dive. Tools: Bash + Read +
Grep. Hard rules baked in (one repo per spawn, no edits, no
recursion).
plugins/cix/tests/workspace-bundle.bats— 10 regressiontests covering presence, frontmatter, manual-only enforcement,
read-only tools, manifest version pin.
Manual-only by design
The
cix-workspaceskill does not auto-trigger. The frontmatterhas no
when_to_use:block, and thedescription:explicitly states"Do not auto-trigger". Invocation is exclusively via
/cix-workspace <task>.Why: the workspace flow is heavier than single-repo
cix search(multi-repo fan-out, sub-agent spawns). Auto-trigger on every prompt
that vaguely mentions "services" would burn context for no reason.
Load it deliberately when you've decided cross-project research is
the right shape of work. Policy may relax once
"is-this-really-cross-project?" heuristics are more reliable.
A bats test pins this — re-adding
when_to_use:fails CI.Doc updates
Install instructions across
workspaces.md, top-levelREADME.md,and
skills/README.mdnow lead with the marketplace plugin install;manual
cp -ris kept as the "legacy" path. All three explicitlycall out that the skill is manual-only.
The top-level
skills/cix-workspace/SKILL.mdis synced with theplugin copy so the two don't drift.
Test plan
bats plugins/cix/tests/— 70/70 green locally (60 existing+ 10 new
workspace-bundle.batsassertions)/plugin marketplace add <local-path>→
/plugin install cix@code-index --scope local→ confirm/cix-workspaceis invokable andcix-workspace-investigatorshows up as a discoverable sub-agent type
🤖 Generated with Claude Code