alexion/skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(skills): require isolated review and test workers

Browse Source
This commit is contained in:
alexion
2026-08-01 18:19:32 -04:00
parent 0f2b13c5f9
commit 40b16b8796
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
skills/review/SKILL.md
View File

@@ -32,8 +32,8 @@ Done when the chosen change set is explicit and reviewers have enough input to j
Run independent dimension reviewers through whatever real context boundary the current harness provides.
A separate agent, worker, subprocess, or documented headless session is sufficient when each reviewer can inspect its dimension without seeing the parent review's intermediate conclusions.
Use one reviewer per dimension when practical.
If no real context boundary is available, state that limitation before reviewing.
Proceed in-process only as an explicitly degraded fallback, and preserve separate report sections.
If no real context boundary is available, stop before reviewing and report that independent review cannot be completed in the current runtime.
Do not replace independent reviewers with in-process role switches.
Use these reviewer files:

4
skills/subagents/SKILL.md
View File

@@ -13,9 +13,9 @@ The supported tool names are `subagent_spawn`, `subagent_batch`, `subagent_list`
If these tools are unavailable, do not pretend that an in-process role switch is a subagent.
State that Pi subagent tools are unavailable in the current runtime.
Do not perform the delegated subagent work in-process unless the caller explicitly permits a degraded fallback.
Do not perform the delegated subagent work in-process.
Done when the run has either a supported subagent tool path or a caller-approved degraded mode.
Done when the run has a supported subagent tool path.
## 2. Prepare a bounded prompt

4
skills/test-driven-development/SKILL.md
View File

@@ -17,8 +17,8 @@ Tests are always written by someone other than the agent doing implementation.
Launch an independent test writer through whatever real context boundary the current harness provides.
A separate agent, worker, subprocess, or documented headless session is sufficient when it cannot see the implementation agent's private backlog.
If no real context boundary is available, state that limitation before writing tests.
Proceed in-process only as an explicitly degraded fallback, and preserve role separation as much as possible.
If no real context boundary is available, stop before writing tests and report that test-driven development cannot be completed in the current runtime.
Do not replace the independent test writer with an in-process role switch.
Do not silently skip the independent-test-writer requirement.
The implementation agent may keep a private behavior backlog.