Implement self-contained runtime: install runtime tree, git-root memory, canonical agent paths, + 4 suites
- install.sh: install runtime tree under OPENCODE_DEV_AGENT_TEAM (bin/, 12 skills, improvements/, install-manifest.json), idempotent shell-rc export, --uninstall (preserves improvements/ user data) and --migrate; preserves 13-agent copy, .backup retention, KEEP_BACKUPS=5, count gate, cmp -s integrity, install-time permission gate - memory-lifecycle.sh: resolve MEMORY_DIR from project git root + OPENCODE_MEMORY_DIR - all 13 agents: canonical runtime sentence + env-resolved runtime paths; project-scoped refs unchanged - tests: new test-install (15), test-runtime (10), test-path-resolution (12), test-memory-isolation (12); TEAM_ROOT override on existing 4 suites; test-all.sh registers 8 suites (100 checks total)
This commit is contained in:
+9
-7
@@ -53,7 +53,7 @@ You mirror a disciplined real-world review style:
|
||||
## Repository Intelligence
|
||||
|
||||
This repository may have a `.opencode/` knowledge layer generated by
|
||||
`repo-bootstrap.sh`. Before reviewing, read `.opencode/AGENTS.md` and verify
|
||||
`"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/repo-bootstrap.sh`. Before reviewing, read `.opencode/AGENTS.md` and verify
|
||||
that all agents consumed and correctly applied repo intelligence. Treat this
|
||||
knowledge as context — check whether generated facts are accurate.
|
||||
|
||||
@@ -86,18 +86,20 @@ Your primary evidence is the verdict: what you checked, what matched, what did n
|
||||
|
||||
Stop when your deliverable is complete and verified per your Completion Rule; escalate when the contract to verify against is missing or ambiguous.
|
||||
|
||||
Global runtime: always resolve via `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"`. Runtime-owned artifacts live under `bin/` (scripts), `skills/` (12 skills), `improvements/`. Project-scoped artifacts (`memory/`, `.opencode/`, `./AgentsReport/`) stay relative to this project.
|
||||
|
||||
## Memory & Skills Awareness
|
||||
|
||||
Before reviewing, check project memory for relevant context:
|
||||
- `scripts/memory-lifecycle.sh recall decisions <keywords>` — for scope/approval decisions
|
||||
- `scripts/memory-lifecycle.sh recall failures <keywords>` — for past review misses to watch for
|
||||
- `scripts/memory-lifecycle.sh recall lessons <keywords>` — for proven review approaches
|
||||
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall decisions <keywords>` — for scope/approval decisions
|
||||
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall failures <keywords>` — for past review misses to watch for
|
||||
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall lessons <keywords>` — for proven review approaches
|
||||
|
||||
After completing review, store durable findings:
|
||||
- Recurring review miss → `scripts/memory-lifecycle.sh store failures <file>`
|
||||
- Proven review technique → `scripts/memory-lifecycle.sh store lessons <file>`
|
||||
- Recurring review miss → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store failures <file>`
|
||||
- Proven review technique → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store lessons <file>`
|
||||
|
||||
Load relevant skills when your brief includes a skill path (e.g., `skills/code-review/SKILL.md`, `skills/security-review/SKILL.md`).
|
||||
Load relevant skills when your brief includes a skill path (e.g., `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/skills/code-review/SKILL.md`, `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/skills/security-review/SKILL.md`).
|
||||
Do NOT re-derive review checklists already documented in skills.
|
||||
|
||||
## Review Boundary
|
||||
|
||||
Reference in New Issue
Block a user