edkuksa/skills
1
0
Fork 0
mirror of https://github.com/mattpocock/skills.git synced 2026-09-12 10:28:06 +07:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #781 from mattpocock/fix/harness-neutral-subagent-language

Browse Source 
fix: make subagent dispatch harness-neutral
This commit is contained in:
Matt Pocock
2026-08-06 14:14:16 +01:00
committed by GitHub
parent 8b36d4fb26 c0d69015e0
commit 7bb49795a1
4 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.changeset/harness-neutral-subagent-language.md
+5
View File
@@ -0,0 +1,5 @@
---
"mattpocock-skills": patch
---
Drop Claude Code's tool and agent-type names from the subagent-dispatch instructions in `code-review`, `codebase-design`, and `improve-codebase-architecture`, so the step is followable on Codex and other harnesses.
skills/engineering/code-review/SKILL.md
-2
View File
@@ -57,8 +57,6 @@ Each smell reads *what it is* → *how to fix*; match it against the diff:
### 4. Spawn both sub-agents in parallel
Send a single message with two `Agent` tool calls. Use the `general-purpose` subagent for both.
**Standards sub-agent prompt** — include:
- The full diff command and commit list.
skills/engineering/codebase-design/DESIGN-IT-TWICE.md
+1 -1
View File
@@ -18,7 +18,7 @@ Show this to the user, then immediately proceed to Step 2. The user reads and th
### 2. Spawn sub-agents
Spawn 3+ sub-agents in parallel using the Agent tool. Each must produce a **radically different** interface for the deepened module.
Spawn 3+ sub-agents in parallel. Each must produce a **radically different** interface for the deepened module.
Prompt each sub-agent with a separate technical brief (file paths, coupling details, dependency category from [DEEPENING.md](DEEPENING.md), what sits behind the seam). The brief is independent of the user-facing problem-space explanation in Step 1. Give each agent a different design constraint:
skills/engineering/improve-codebase-architecture/SKILL.md
+1 -1
View File
@@ -24,7 +24,7 @@ This command is _informed_ by the project's domain model and built on a shared d
Read the project's domain glossary (`CONTEXT.md`) and any ADRs in the area you're touching first.
Then use the Agent tool with `subagent_type=Explore` to walk the codebase. Don't follow rigid heuristics — explore organically and note where you experience friction:
Then spawn a sub-agent to walk the codebase. Don't follow rigid heuristics — explore organically and note where you experience friction:
- Where does understanding one concept require bouncing between many small modules?
- Where are modules **shallow** — interface nearly as complex as the implementation?