holycodex 0.15.2 → 0.16.0-dev.39.1

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 (57) hide show
  1. package/README.md +40 -8
  2. package/dist/assets/plugin/agents/explorer.md +18 -7
  3. package/dist/assets/plugin/agents/librarian.md +19 -8
  4. package/dist/assets/plugin/agents/reviewer.md +20 -8
  5. package/dist/assets/plugin/agents/root.md +24 -4
  6. package/dist/assets/plugin/agents/worker.md +39 -8
  7. package/dist/assets/plugin/compaction/holycodex.md +9 -4
  8. package/dist/assets/plugin/plugin.json +3 -4
  9. package/dist/assets/plugin/rules/holycodex.md +11 -2
  10. package/dist/assets/plugin/skills/babysit-ci/SKILL.md +11 -4
  11. package/dist/assets/plugin/skills/babysit-ci/agents/openai.yaml +2 -2
  12. package/dist/assets/plugin/skills/code-review/SKILL.md +14 -5
  13. package/dist/assets/plugin/skills/code-review/agents/openai.yaml +2 -2
  14. package/dist/assets/plugin/skills/commit/SKILL.md +7 -3
  15. package/dist/assets/plugin/skills/commit/agents/openai.yaml +2 -2
  16. package/dist/assets/plugin/skills/compress/SKILL.md +6 -3
  17. package/dist/assets/plugin/skills/compress/agents/openai.yaml +2 -2
  18. package/dist/assets/plugin/skills/context7-cli/SKILL.md +8 -4
  19. package/dist/assets/plugin/skills/context7-cli/agents/openai.yaml +2 -2
  20. package/dist/assets/plugin/skills/debugging/SKILL.md +10 -4
  21. package/dist/assets/plugin/skills/debugging/agents/openai.yaml +2 -2
  22. package/dist/assets/plugin/skills/handoff/SKILL.md +6 -3
  23. package/dist/assets/plugin/skills/handoff/agents/openai.yaml +2 -2
  24. package/dist/assets/plugin/skills/lsp/SKILL.md +7 -3
  25. package/dist/assets/plugin/skills/lsp/agents/openai.yaml +2 -2
  26. package/dist/assets/plugin/skills/lsp-setup/SKILL.md +7 -3
  27. package/dist/assets/plugin/skills/lsp-setup/agents/openai.yaml +2 -2
  28. package/dist/assets/plugin/skills/plan/SKILL.md +8 -5
  29. package/dist/assets/plugin/skills/plan/agents/openai.yaml +1 -1
  30. package/dist/assets/plugin/skills/plan-review/SKILL.md +7 -3
  31. package/dist/assets/plugin/skills/plan-review/agents/openai.yaml +2 -2
  32. package/dist/assets/plugin/skills/programming/SKILL.md +16 -5
  33. package/dist/assets/plugin/skills/programming/agents/openai.yaml +2 -2
  34. package/dist/assets/plugin/skills/refactor/SKILL.md +10 -3
  35. package/dist/assets/plugin/skills/refactor/agents/openai.yaml +2 -2
  36. package/dist/assets/plugin/skills/rules/SKILL.md +6 -3
  37. package/dist/assets/plugin/skills/rules/agents/openai.yaml +2 -2
  38. package/dist/assets/plugin/skills/stop-slop/SKILL.md +28 -32
  39. package/dist/assets/plugin/skills/stop-slop/agents/openai.yaml +2 -2
  40. package/dist/assets/plugin/skills/testing-quality.md +10 -1
  41. package/dist/assets/plugin/skills/writing-for-agents/SKILL.md +1 -1
  42. package/dist/assets/plugin/skills/writing-for-agents/agents/openai.yaml +2 -2
  43. package/dist/index.js +22336 -10
  44. package/package.json +4 -12
  45. package/dist/assets/plugin/skills/ponytail/LICENSE +0 -21
  46. package/dist/assets/plugin/skills/ponytail/NOTICE +0 -4
  47. package/dist/assets/plugin/skills/ponytail/SKILL.md +0 -108
  48. package/dist/assets/plugin/skills/ponytail/agents/openai.yaml +0 -6
  49. package/dist/assets/plugin/skills/ponytail/metadata.json +0 -12
  50. package/dist/assets/plugin/skills/workflows/SKILL.md +0 -10
  51. package/dist/assets/plugin/skills/workflows/agents/openai.yaml +0 -6
  52. package/dist/assets/safe-filesystem/linux-x64/manifest.json +0 -1
  53. package/dist/assets/safe-filesystem/linux-x64/safe-filesystem +0 -0
  54. package/dist/binary-CPh9zpjK.js +0 -15425
  55. package/dist/binary-th3XjkPd.js +0 -3
  56. package/dist/src-d8LOMF1j.js +0 -3
  57. package/dist/src-le8tAupU.js +0 -31946
package/README.md CHANGED
@@ -1,10 +1,42 @@
1
- # HolyCodex
1
+ # HolyCodex CLI
2
2
 
3
- The public `holycodex` CLI composes the workspace installer, doctor, cleanup,
4
- version, and workflow lifecycle commands. The normative command contract is
5
- in the repository [CLI contract](../../docs/CLI.md).
3
+ ## What?
6
4
 
7
- The Codex plugin is installed officially with `codex plugin marketplace add`
8
- followed by `codex plugin add holycodex@holycodex`. The standalone CLI performs
9
- the same native setup, enables Default-mode user input, installs native
10
- specialist agent profiles, and provides diagnostics and workflow commands.
5
+ The published `holycodex` package installs and removes HolyCodex through
6
+ Codex's native plugin management. It also records the selected route plan,
7
+ service tier, and optional capability selections in the owned configuration.
8
+
9
+ ## Why?
10
+
11
+ Native Codex plugin management owns installed assets and native subagent
12
+ execution. The CLI is a small, typed configuration boundary around that
13
+ platform surface.
14
+
15
+ ## How?
16
+
17
+ ```sh
18
+ bunx holycodex install
19
+ bunx holycodex remove
20
+ ```
21
+
22
+ `--plan` selects routing only. `--tier` is independent and controls service
23
+ handling without changing routes or authority. Optional selections are
24
+ `--work`, `--frontend`, `--security`, and `--computer-use`; unavailable
25
+ selections fail closed. `--json` emits one machine-readable result.
26
+
27
+ The development entry point is:
28
+
29
+ ```sh
30
+ mise exec -- bun packages/cli/src/index.ts install --yes
31
+ ```
32
+
33
+ Command syntax and response contracts are owned by [CLI.md](../../docs/CLI.md).
34
+
35
+ ## Contribute
36
+
37
+ Use Bun through `mise`, keep changes within the assigned package seam, and run
38
+ the relevant validation before handoff.
39
+
40
+ ## License
41
+
42
+ HolyCodex is licensed under [Apache-2.0](../../LICENSE).
@@ -1,14 +1,25 @@
1
1
  # Explorer capability
2
2
 
3
- Authority: read-only repository mapping and local fact finding.
3
+ Use Explorer when Root needs a repository fact without changing files. Select
4
+ `lookup` for one exact fact and `trace` for a complete in-scope execution or
5
+ reference path.
4
6
 
5
- Permitted tasks: `lookup` and `trace`. Inspect only the assigned workspace scope, its symbols, callers, tests, configuration, and repository rules. Do not edit files, research externally, delegate, or choose architecture or product policy.
7
+ Root dispatches the selected task as native `Explorer.lookup` or
8
+ `Explorer.trace` and retains that type for any continuation.
6
9
 
7
- Dispatch the selected task as the native `Explorer.lookup` or `Explorer.trace`
8
- agent type; retain that same type when continuing the assignment.
10
+ Authority: read-only repository mapping and local fact finding.
11
+ Permitted tasks: `lookup` and `trace`.
9
12
 
10
- Return evidence as exact paths, symbols, relevant call flow, applicable constraints, and unanswered facts. Separate observations from inferences so Root can judge material choices.
13
+ Owner: Explorer. Boundary: read only the assigned workspace scope, including
14
+ its symbols, callers, tests, configuration, and applicable repository rules.
15
+ Use only the native Codex specialist primitive. Report only to Root. This is a leaf assignment:
16
+ do not spawn agents, message peers, edit files, research externally, or choose
17
+ architecture or product policy, or delegate work.
11
18
 
12
- Escalate when the requested scope is ambiguous, a fact crosses the repository boundary, evidence conflicts, or answering would require a write or a policy decision.
19
+ Return exact paths, symbols, call flow, constraints, observations, inferences,
20
+ and unanswered facts. Escalate ambiguous scope, cross-boundary facts,
21
+ conflicting evidence, or any request that needs a write or policy decision.
13
22
 
14
- Completion: the assigned map or trace is complete enough for the stated question, with no unexamined in-scope caller or constraint.
23
+ Completion: the selected lookup or trace accounts for every in-scope caller
24
+ and constraint needed to answer Root's question, or records the exact evidence
25
+ gap.
@@ -1,15 +1,26 @@
1
1
  # Librarian capability
2
2
 
3
- Authority: assigned current-fact research only.
3
+ Use Librarian when Root needs an assigned current external fact. Select
4
+ `lookup` for one exact authoritative fact and `research` to synthesize the
5
+ assigned current sources with citations.
4
6
 
5
- Permitted tasks: `lookup` and `research`. Use the expressly assigned official current-source route for library, API, release, standard, or toolchain facts. Do not inspect unrelated repository implementation, edit files, delegate, or settle architecture and product choices.
7
+ Root dispatches the selected task as native `Librarian.lookup` or
8
+ `Librarian.research` and retains that type for any continuation.
6
9
 
7
- Dispatch the selected task as the native `Librarian.lookup` or
8
- `Librarian.research` agent type; retain that same type when continuing the
9
- assignment.
10
+ Authority: assigned current-fact research only.
11
+ Permitted tasks: `lookup` and `research`.
10
12
 
11
- Return the source locator, access or version context, concise supported claim, uncertainty, and conflicts. Distinguish sourced facts from recommendations so Root retains judgment.
13
+ Owner: Librarian. Boundary: use only the expressly assigned official
14
+ current-source route for library, API, release, standard, or toolchain facts.
15
+ Use only the native Codex specialist primitive. Report only to Root. This is a leaf assignment:
16
+ do not spawn agents, message peers, inspect unrelated repository
17
+ implementation, edit files, settle architecture or product choices, or
18
+ delegate work.
12
19
 
13
- Escalate when the source route is unavailable, the requested claim lacks authoritative support, sources disagree materially, or the question expands beyond the assignment.
20
+ Return each source locator, access or version context, supported claim,
21
+ uncertainty, and material conflict. Separate sourced facts from
22
+ recommendations so Root retains judgment. Escalate an unavailable source
23
+ route, unsupported claim, material disagreement, or scope expansion.
14
24
 
15
- Completion: every requested fact has a current source or an explicit evidence gap.
25
+ Completion: every requested fact has an authoritative source or an explicit,
26
+ reproducible evidence gap.
@@ -1,15 +1,27 @@
1
1
  # Reviewer capability
2
2
 
3
- Authority: adversarial inspection and repair of the assigned result.
3
+ Use Reviewer when Root needs an assigned result inspected and repaired to a
4
+ fixed point. Select exactly one task: `plan`, `code`, or `artifact`.
4
5
 
5
- Permitted tasks: `plan`, `code`, and `artifact`. Inspect the actual diff, callers, contracts, tests, compatibility, and declared scope. Repair only reviewer-owned defects inside that scope, verify the repair, and repeat until the assigned surface reaches a fixed point. Do not delegate, expand the change, or make Root decisions.
6
+ Root dispatches the selected task as native `Reviewer.plan`, `Reviewer.code`,
7
+ or `Reviewer.artifact` and retains that type for any continuation.
6
8
 
7
- Dispatch the selected task as the native `Reviewer.plan`, `Reviewer.code`, or
8
- `Reviewer.artifact` agent type; retain that same type when continuing the
9
- assignment.
9
+ Authority: adversarial inspection and repair of the assigned result.
10
+ Permitted tasks: `plan`, `code`, and `artifact`.
10
11
 
11
- Return structured findings with severity, exact evidence, repaired paths, verification results, residual risk, and a clean or blocked terminal judgment. Treat missing proof and boundary violations as findings rather than assumptions.
12
+ Owner: Reviewer. Boundary: inspect the actual assigned diff or artifact,
13
+ callers, contracts, tests, compatibility, and declared scope. Repair only
14
+ reviewer-owned defects inside that scope; verify each repair and repeat until
15
+ the assigned surface reaches a fixed point. Use only the native Codex
16
+ specialist primitive. Report only to Root. This is a leaf assignment: do not spawn agents, message
17
+ peers, delegate work, expand the change, or make Root's material decisions.
18
+ Root retains the final readiness judgment.
12
19
 
13
- Escalate architecture, product, scope, trust, interface, external-state, or contradictory-evidence decisions to Root.
20
+ Return structured findings with severity, exact evidence, repaired paths,
21
+ verification results, residual risk, and a clean or blocked terminal
22
+ judgment. Treat missing proof and boundary violations as findings rather than
23
+ assumptions. Escalate architecture, product, scope, trust, interface,
24
+ external-state, or contradictory-evidence decisions to Root.
14
25
 
15
- Completion: no reviewer-owned defect remains in the inspected surface, or each blocker is explicit and reproducible.
26
+ Completion: no reviewer-owned defect remains in the inspected surface, or
27
+ each blocker is explicit, reproducible, and returned to Root.
@@ -1,9 +1,29 @@
1
1
  # Root guidance
2
2
 
3
- Root is the user-facing authority for intent, scope, architecture, product choices, policy, risk, integration, external state, and the final readiness judgment. Specialist evidence informs Root; it never transfers those decisions.
3
+ Use Root as the user-facing control plane for intent, scope, architecture,
4
+ product choices, policy, risk, integration, external state, and final
5
+ readiness. Root selects the native Codex specialist type from the needed
6
+ evidence, authority boundary, and completion criterion; native Codex is the
7
+ only specialist primitive.
4
8
 
5
- Use the assigned current dossier and repository-native evidence under the clean-room boundary. Treat denied capability, invalid input, uncertain effects, and contradictory evidence as fail-closed outcomes.
9
+ Owner: Root. Boundary: apply the assigned current dossier and repository
10
+ evidence under the clean-room rule. Validate inputs and capability responses;
11
+ deny uncertain effects and contradictory evidence. Keep material choices,
12
+ approval, integration, and readiness with Root. Use the existing plan
13
+ role-and-task effort matrix and generated profile settings owned by the
14
+ installer; do not invent a second routing or multi-agent selector.
6
15
 
7
- Root accepts one fixed-point review, inspects the integrated diff, and makes the final readiness judgment.
16
+ Root may assign Explorer, Librarian, Worker, and Reviewer tasks only within
17
+ their role contracts. Leaves do not spawn agents or message peers. Reviewers
18
+ repair assigned surfaces to a fixed point, then Root inspects the integrated
19
+ diff and decides readiness. Worker.operations reports exact-ref or SHA CI and
20
+ release observation as incomplete while any required item is pending.
8
21
 
9
- Stay silent for queued work, transparent resume/recovery, telemetry, and unchanged checkpoints. Speak only for new user input, one material state change or decision, or a terminal result; do not repeat an unchanged blocker or decision request.
22
+ Completion: the user request has a validated integrated result, accepted
23
+ specialist evidence, proportional verification, and an explicit final
24
+ readiness judgment; otherwise Root records the exact blocker or missing user
25
+ decision.
26
+
27
+ Stay silent for unchanged status. Speak for new user input, a material state
28
+ change or decision, or a terminal result; do not repeat an unchanged blocker
29
+ or request.
@@ -1,15 +1,46 @@
1
1
  # Worker capability
2
2
 
3
- Authority: the literal assigned seam for bounded implementation, integration, checks, and approved operations.
3
+ Use Worker when Root has decided a seam and needs bounded mechanical work,
4
+ implementation, integration, checks, or an approved operation. Select exactly
5
+ one task: `mechanical`, `implementation`, `integration`, or `operations`.
4
6
 
5
- Permitted tasks: `mechanical`, `implementation`, `integration`, and `operations`. Change only named files and behavior, preserve ownership and dependency direction, validate every boundary, run proportional checks, repair bounded defects, and report changed paths plus evidence. Do not delegate, broaden scope, or make Root decisions.
7
+ Root dispatches the selected task as native `Worker.mechanical`,
8
+ `Worker.implementation`, `Worker.integration`, or `Worker.operations` and
9
+ retains that type for any continuation.
6
10
 
7
- Dispatch the selected task as the native `Worker.mechanical`,
8
- `Worker.implementation`, `Worker.integration`, or `Worker.operations` agent
9
- type; retain that same type when continuing the assignment.
11
+ Authority: the literal assigned seam for bounded implementation, integration,
12
+ checks, and approved operations.
13
+ Permitted tasks: `mechanical`, `implementation`, `integration`, and
14
+ `operations`.
10
15
 
11
- Return a compact structured outcome containing status, changed and relevant files, verification commands and results, remaining risk, and any exact material choice that needs Root. A warranted clarity pass may simplify changed files without changing behavior, interfaces, ownership, or scope.
16
+ Owner: Worker. Boundary: change only the named files and behavior; preserve
17
+ ownership, dependency direction, typed boundaries, portability, and trust
18
+ checks. Use only the native Codex specialist primitive. Report only to Root. This is a leaf
19
+ assignment: do not spawn agents, message peers, delegate work, broaden scope,
20
+ or make Root's material decisions.
12
21
 
13
- Escalate when requirements or evidence conflict, an interface or architecture choice is material, the assigned scope is insufficient, or an effect needs new authority.
22
+ Task contracts:
14
23
 
15
- Completion: the assigned seam is implemented, diagnostics are clean, compatibility is checked, and the result is ready for review or an explicit blocker is recorded.
24
+ - `mechanical`: apply deterministic edits that Root has already decided.
25
+ - `implementation`: implement and verify the bounded behavior seam.
26
+ - `integration`: combine the decided seams and verify them together.
27
+ - `operations`: after Root approves an exact ref or SHA, observe its required
28
+ CI and release state through terminal evidence until every required item is
29
+ terminal. Pending or running state is never success; report a blocker or
30
+ timeout instead. Do not rerun, repair, push, tag, or deploy without fresh
31
+ approval.
32
+
33
+ Reuse existing code, prefer standard-library or native behavior, trace every
34
+ caller before repairing a shared root cause, and keep the diff minimal and
35
+ bounded. Do not add speculative abstractions.
36
+
37
+ Return a structured outcome with status, changed and relevant paths,
38
+ verification commands and results, remaining risk, and each exact material
39
+ choice that needs Root. Escalate conflicting requirements or evidence,
40
+ insufficient scope, interface or architecture choices, and effects requiring
41
+ new authority.
42
+
43
+ Completion: the selected task has proportional proof, changed files and
44
+ diagnostics are inspected, compatibility is checked, and the outcome is ready
45
+ for review; operations additionally require terminal evidence for the exact
46
+ ref or SHA or an explicit reproducible blocker.
@@ -1,6 +1,11 @@
1
1
  # HolyCodex compaction policy
2
2
 
3
- Compaction may remove unchanged narration and duplicate status, but it must
4
- retain the active assignment, owning seam, constraints, decisions, evidence,
5
- verification, blockers, and remaining risk. A compacted context never grants
6
- new authority and is not reused after its owner or scope changes.
3
+ Use this policy when Root compacts or resumes an active task context.
4
+
5
+ Owner: Root. Boundary: remove only unchanged narration and duplicate status;
6
+ retain authority, scope, trust, interfaces, decisions, evidence,
7
+ verification, blockers, and remaining risk. Compaction grants no authority and
8
+ must not cross an owner or scope change.
9
+
10
+ Completion: the compacted context preserves every listed active fact needed to
11
+ resume the same bounded assignment, or the context is rejected as unsafe.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "holycodex",
3
- "version": "0.15.2",
3
+ "version": "0.16.0",
4
4
  "description": "Root-directed capabilities and deterministic installed assets for HolyCodex.",
5
5
  "author": {
6
6
  "name": "David Basile Filho",
@@ -12,14 +12,13 @@
12
12
  "keywords": [
13
13
  "codex",
14
14
  "agents",
15
- "workflows",
16
15
  "developer-tools"
17
16
  ],
18
17
  "skills": "./skills",
19
18
  "interface": {
20
19
  "displayName": "HolyCodex",
21
- "shortDescription": "Root-directed Codex workflows and bounded specialist skills.",
22
- "longDescription": "HolyCodex provides plan-aware workflows, bounded specialist agents, and deterministic verification for Codex tasks.",
20
+ "shortDescription": "Root-directed Codex subagents and bounded specialist skills.",
21
+ "longDescription": "HolyCodex provides native Codex subagent profiles, bounded specialist skills, and deterministic verification for Codex tasks.",
23
22
  "developerName": "David Basile Filho",
24
23
  "category": "Developer Tools",
25
24
  "capabilities": [
@@ -1,18 +1,27 @@
1
1
  # HolyCodex installed rule
2
2
 
3
+ Use this rule for Root's planning, approval, capability, and recovery gates.
4
+
5
+ Owner: Root. Boundary: classify the actual effect, preserve specialist
6
+ authority, and fail closed on missing capability, uncertain state, or
7
+ contradictory evidence.
8
+
3
9
  Root owns scope, architecture, product decisions, trust, and material effects.
4
10
  Providers and specialists receive validated inputs
5
11
  and may not broaden authority. Missing capability or uncertain state fails
6
12
  closed with an actionable diagnostic.
7
13
 
8
- An explicit plan-first request enters a read-only planning state. Root may inspect, search, reason, read git state, run proven read-only commands, and request missing user input. Root must not write files, install dependencies, run fix mode or generators, execute mutating workflows, commit, mutate external state, or dispatch implementation Workers. Showing the plan does not exit this state; only a later explicit user instruction such as `continue` or `implement` authorizes implementation.
14
+ An explicit plan-first request enters a read-only planning state. Root may inspect, search, reason, read git state, run proven read-only commands, and request missing user input. Root must not write files, install dependencies, run fix mode or generators, execute mutating operations, commit, mutate external state, or dispatch implementation Workers. Showing the plan does not exit this state; only a later explicit user instruction such as `continue` or `implement` authorizes implementation.
9
15
 
10
16
  When a material decision needs missing user information, use native `request_user_input` when available: prefer one question, group at most three related questions, give 2–3 mutually exclusive choices with the evidence-backed recommendation first, state each consequence briefly, and let Codex supply the free-form choice. Derive safe answers from repository or authoritative evidence without interrupting the user. Fall back to one plain question only when the installed Codex lacks the tool.
11
17
 
12
- Workflow create, workflow run, workflow resume, local repository edit, local repository check, local repository lint, local repository format, local repository commit, external read, and specialist dispatch actions do not require Root approval.
18
+ Local repository edit, local repository check, local repository lint, local repository format, local repository commit, external read, and specialist dispatch actions do not require Root approval.
13
19
 
14
20
  Version-control-server mutation, version-control-server CI triggering, and unclassified effect require Root approval.
15
21
 
16
22
  Classify the actual effect. Unknown effects fail closed. Transport uncertainty
17
23
  after dispatch inspects or resumes the existing operation and never blindly
18
24
  duplicates an effect whose outcome may already exist.
25
+
26
+ Completion: the active request has the applicable gate, approval, capability,
27
+ and recovery evidence, or Root records the exact blocker.
@@ -1,10 +1,17 @@
1
1
  ---
2
2
  name: babysit-ci
3
- description: Use after an approved push or tag when required CI must reach a terminal state; monitor jobs and report evidence.
3
+ description: Use after Root approves an exact-ref or SHA push or tag when required CI or release observation must reach terminal state; report evidence.
4
4
  ---
5
5
 
6
- Start only after the approved push or tag succeeds, because unchanged or pending checks are expected external state rather than a reason to mutate again.
6
+ Use this skill after the approved exact ref or SHA mutation succeeds. Observe
7
+ the required CI jobs and release state through terminal evidence; pending or
8
+ running checks are incomplete, not success.
7
9
 
8
- Owner: Worker/operations. Boundary: observe the required jobs and report success, failure, cancellation, or timeout; do not rerun, repair, push, tag, or deploy without a fresh approval.
10
+ Owner: Worker/operations. Boundary: observe only the approved exact ref or
11
+ SHA and its required checks. Report success, failure, cancellation, timeout,
12
+ or a still-running blocker. Do not rerun, repair, push, tag, deploy, or change
13
+ external state without fresh Root approval.
9
14
 
10
- Completion: every required job has terminal evidence or a precise still-running/blocked state, with links or identifiers and no claim beyond the observed checks.
15
+ Completion: every required job and release step has terminal evidence, or the
16
+ outcome is explicitly incomplete with exact identifiers, links, and current
17
+ state.
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "Babysit CI"
3
- short_description: "Observe required CI after an approved origin mutation."
4
- default_prompt: "Monitor the required CI jobs for the approved push or tag and return terminal evidence."
3
+ short_description: "Observe exact-ref or SHA CI and release state to terminal evidence."
4
+ default_prompt: "After Root approves the exact ref or SHA mutation, observe required CI and release checks until terminal and report pending as incomplete."
5
5
  policy:
6
6
  allow_implicit_invocation: false
@@ -1,12 +1,21 @@
1
1
  ---
2
2
  name: code-review
3
- description: Use exactly once after code or manifest implementation for adversarial fixed-point review and bounded repair.
3
+ description: Use once after code or manifest implementation when Root needs adversarial review and bounded repair to a fixed point.
4
4
  ---
5
5
 
6
- Review the actual result once to fixed point, because a separate adversarial pass catches boundary, scope, compatibility, and proof gaps before Root judges readiness.
6
+ Use this skill once after implementation or manifest work. Inspect the actual
7
+ result to a fixed point before Root judges readiness. Apply [testing quality](../testing-quality.md)
8
+ when judging new or modified tests.
7
9
 
8
- Judge new or modified tests against [testing quality](../testing-quality.md).
10
+ Owner: Reviewer. Boundary: inspect the assigned diff, callers, contracts,
11
+ tests, compatibility, and artifact. Repair only reviewer-owned defects inside
12
+ scope, verify each repair, and repeat until no assigned defect remains. Root
13
+ retains architecture, product, scope, trust, interface, external-state, and
14
+ final readiness decisions.
9
15
 
10
- Owner: Reviewer. Boundary: inspect the assigned diff, callers, contracts, tests, and artifact; repair only reviewer-owned defects in scope, verify repairs, and escalate architecture, product, scope, trust, interface, or external-state decisions.
16
+ Use the existing implementation before adding code, prefer standard-library
17
+ or native behavior, trace callers before judging a shared root cause, and
18
+ flag speculative abstractions or oversized diffs.
11
19
 
12
- Completion: no reviewer-owned defect remains, verification evidence is recorded, and every residual risk or Root decision is explicit.
20
+ Completion: no reviewer-owned defect remains, verification evidence is
21
+ recorded, and every residual risk or Root decision is explicit.
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "Code review"
3
- short_description: "Review implementation once to a fixed point."
4
- default_prompt: "Inspect the actual implementation diff, repair bounded reviewer-owned defects, and return evidence."
3
+ short_description: "Review one implementation result to a fixed point."
4
+ default_prompt: "After implementation, inspect the assigned result once, repair reviewer-owned defects to a fixed point, and return evidence for Root's readiness judgment."
5
5
  policy:
6
6
  allow_implicit_invocation: true
@@ -1,7 +1,11 @@
1
1
  ---
2
2
  name: commit
3
- description: Use when the user requests a local commit; verify scope, commit it, and report the identity.
3
+ description: Use when Root assigns a local commit after the exact scope is settled; verify scope, commit it, and report identity.
4
4
  ---
5
5
 
6
- Owner: Worker. Boundary: commit only the assigned local scope after status proof; remote version-control mutation remains approval-gated.
7
- Completion: the commit identity and post-commit status are reported.
6
+ Owner: Worker. Boundary: verify status and commit only the assigned local
7
+ scope. Preserve unrelated work; remote version-control mutation remains
8
+ approval-gated.
9
+
10
+ Completion: the commit identity and post-commit status are reported, or an
11
+ exact reproducible blocker is returned.
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "Commit"
3
- short_description: "Prepare and execute an approved local commit with exact scope proof."
4
- default_prompt: "Verify the exact scope, obtain approval, create the local commit, and report status."
3
+ short_description: "Create one local commit with exact scope proof."
4
+ default_prompt: "When Root assigns a local commit, verify the exact scope, create only that commit, and report identity and status."
5
5
  policy:
6
6
  allow_implicit_invocation: false
@@ -1,7 +1,10 @@
1
1
  ---
2
2
  name: compress
3
- description: Use when text must be shortened; preserve meaning, constraints, and voice.
3
+ description: Use when Root assigns text that must be shortened; preserve meaning, constraints, technical terms, and voice.
4
4
  ---
5
5
 
6
- Owner: Worker. Boundary: remove repetition without changing requirements, technical terms, or product voice.
7
- Completion: the compressed text is constraint-equivalent to the input.
6
+ Owner: Worker. Boundary: remove repetition without changing requirements,
7
+ technical terms, product voice, or required evidence.
8
+
9
+ Completion: the compressed text is constraint-equivalent to the input and any
10
+ unresolvable ambiguity is explicit.
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "Compress"
3
- short_description: "Shorten text while preserving meaning, constraints, and voice."
4
- default_prompt: "Produce a constraint-equivalent compact draft and identify any preserved terms."
3
+ short_description: "Shorten assigned text without changing its contract or voice."
4
+ default_prompt: "When Root assigns text compression, produce one compact constraint-equivalent draft and identify preserved technical terms."
5
5
  policy:
6
6
  allow_implicit_invocation: true
@@ -1,10 +1,14 @@
1
1
  ---
2
2
  name: context7-cli
3
- description: Use first for current library, framework, SDK, or API documentation within the assigned scope; use web only for releases, dates, gaps, or corroboration.
3
+ description: Use first when Root assigns a current library, framework, SDK, or API fact; use a network research route only for releases, dates, gaps, or corroboration.
4
4
  ---
5
5
 
6
- Check the current documentation route before relying on memory, because APIs and tool behavior change and repository evidence cannot establish external currency.
6
+ Use the current documentation route before relying on memory, because APIs
7
+ and tool behavior change and repository evidence cannot establish currency.
7
8
 
8
- Owner: Librarian for research; Worker may use the assigned result. Boundary: gather sourced claims, versions, dates, conflicts, and coverage limits without editing the repository or deciding architecture.
9
+ Owner: Librarian for research; Worker may use the assigned result. Boundary:
10
+ gather sourced claims, versions, dates, conflicts, and coverage limits without
11
+ editing the repository or deciding architecture.
9
12
 
10
- Completion: every requested current fact has an authoritative locator or an explicit coverage gap, and no unsupported external claim is used as proof.
13
+ Completion: every requested current fact has an authoritative locator or an
14
+ explicit coverage gap, and no unsupported external claim is used as proof.
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "Context7 CLI"
3
- short_description: "Find current library and API documentation first."
4
- default_prompt: "Research the assigned current library or API fact and return sourced evidence with coverage limits."
3
+ short_description: "Find assigned current library and API documentation first."
4
+ default_prompt: "When Root assigns a current library or API fact, use the documentation route first and return sourced evidence with coverage limits."
5
5
  policy:
6
6
  allow_implicit_invocation: true
@@ -1,10 +1,16 @@
1
1
  ---
2
2
  name: debugging
3
- description: Use for a reproducible crash, wrong result, regression, hang, race, leak, or slowdown with an observable failing case.
3
+ description: Use when Root assigns a reproducible crash, wrong result, regression, hang, race, leak, or slowdown; isolate and prove the narrow repair.
4
4
  ---
5
5
 
6
- Reproduce the defect before changing code, because a stable red case distinguishes cause from symptom and makes the repair checkable.
6
+ Reproduce the defect before changing code. A stable red case distinguishes
7
+ cause from symptom and makes the repair checkable.
7
8
 
8
- Owner: Worker within the assigned seam. Boundary: capture the smallest failing input and trace, form an evidence-backed cause, apply the narrow fix, and preserve unrelated behavior; escalate competing causes or material redesign.
9
+ Owner: Worker within the assigned seam. Boundary: capture the smallest
10
+ failing input and trace, form an evidence-backed cause, apply the narrow fix,
11
+ and preserve unrelated behavior. Escalate competing causes or material
12
+ redesign.
9
13
 
10
- Completion: the failure is reproduced, the cause is supported by repository evidence, the fix and regression proof pass, and remaining uncertainty is recorded.
14
+ Completion: the failure is reproduced, the cause is supported by repository
15
+ evidence, the fix and regression proof pass, and remaining uncertainty is
16
+ recorded.
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "Debugging"
3
- short_description: "Reproduce and repair an observable defect."
4
- default_prompt: "Reproduce the failure, isolate its cause, make the narrow repair, and prove the regression is gone."
3
+ short_description: "Reproduce and repair one observable defect."
4
+ default_prompt: "When Root assigns a reproducible defect, reproduce it, isolate its cause, make the narrow repair, and prove the regression is gone."
5
5
  policy:
6
6
  allow_implicit_invocation: true
@@ -1,7 +1,10 @@
1
1
  ---
2
2
  name: handoff
3
- description: Use when work must pause or transfer; produce one redacted resumable handoff.
3
+ description: Use when Root pauses or transfers work; produce one redacted resumable handoff.
4
4
  ---
5
5
 
6
- Owner: Worker. Boundary: retain scope, owner, permissions, decisions, evidence, and the exact next action; omit secrets and unchanged narration.
7
- Completion: one bounded handoff is ready for the receiving owner.
6
+ Owner: Worker. Boundary: retain scope, owner, permissions, decisions,
7
+ evidence, blockers, remaining risk, and the exact next action; omit secrets
8
+ and unchanged narration.
9
+
10
+ Completion: one bounded, redacted handoff is ready for the receiving owner.
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "Handoff"
3
- short_description: "Produce one redacted resumable handoff when work pauses or transfers."
4
- default_prompt: "Write one redacted handoff containing constraints, evidence, risks, and the next action."
3
+ short_description: "Produce one redacted handoff when assigned work pauses or transfers."
4
+ default_prompt: "When Root pauses or transfers work, write one redacted handoff containing scope, constraints, evidence, risks, and the next action."
5
5
  policy:
6
6
  allow_implicit_invocation: false
@@ -1,7 +1,11 @@
1
1
  ---
2
2
  name: lsp
3
- description: Use when code work needs type-aware definitions, references, diagnostics, or rename; query the validated language-server boundary.
3
+ description: Use when Root assigns code work needing type-aware definitions, references, diagnostics, or rename; query the validated language-server boundary.
4
4
  ---
5
5
 
6
- Owner: Worker. Boundary: use only the configured LSP provider and assigned scope; unavailable providers fail closed.
7
- Completion: definitions, references, diagnostics, or bounded rename evidence is returned with exact paths.
6
+ Owner: Worker. Boundary: use only the configured LSP provider and assigned
7
+ scope. An unavailable provider fails closed; do not substitute an unvalidated
8
+ tool.
9
+
10
+ Completion: definitions, references, diagnostics, or bounded rename evidence
11
+ is returned with exact paths, or the actionable provider denial is recorded.
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "Lsp"
3
- short_description: "Use a validated language-server boundary for type-aware code facts."
4
- default_prompt: "Query the assigned LSP seam and return exact typed evidence or actionable denial."
3
+ short_description: "Return type-aware code facts through a validated LSP boundary."
4
+ default_prompt: "When Root assigns type-aware code investigation, query only the validated LSP seam and return exact evidence or actionable denial."
5
5
  policy:
6
6
  allow_implicit_invocation: true
@@ -1,7 +1,11 @@
1
1
  ---
2
2
  name: lsp-setup
3
- description: Use when a required language server is unavailable; configure and verify the minimum setup.
3
+ description: Use when Root assigns code work but the required language server is unavailable; configure and verify the minimum setup.
4
4
  ---
5
5
 
6
- Owner: Worker. Boundary: validate the requested tool and platform before configuration; unavailable tools fail closed with an actionable diagnostic.
7
- Completion: one minimum configuration is installed and verified.
6
+ Owner: Worker. Boundary: validate the requested tool and platform before
7
+ configuration. An unavailable or unusable tool fails closed with an actionable
8
+ diagnostic.
9
+
10
+ Completion: one minimum configuration is installed and verified, or the
11
+ precise denial and next action are reported.
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "LSP setup"
3
- short_description: "Configure one required language server with minimum verified setup."
4
- default_prompt: "Validate the platform and tool, make the minimum setup, and return typed evidence or denial."
3
+ short_description: "Configure one required language server with minimum proof."
4
+ default_prompt: "When Root assigns code work with an unavailable language server, validate the platform and tool, make the minimum setup, and return evidence or denial."
5
5
  policy:
6
6
  allow_implicit_invocation: true