admin/dev_agent_team
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Implement self-contained runtime: install runtime tree, git-root memory, canonical agent paths, + 4 suites

Browse Source 
- 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:
Your Name
2026-09-08 10:17:38 -04:00
parent 03be6211ed
commit 61241c3a82
25 changed files with 1528 additions and 130 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/toolsmith.md
+8 -6
View File
@@ -49,7 +49,7 @@ RECOGNIZE PATTERN → DEFINE RULE → DESIGN MINIMAL TOOL → IMPLEMENT → VERI
## Repository Intelligence
This repository may have a `.opencode/` knowledge layer generated by
`repo-bootstrap.sh`. Before automating, read `.opencode/AGENTS.md` and
`"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/repo-bootstrap.sh`. Before automating, read `.opencode/AGENTS.md` and
`.opencode/skills/repo-context/SKILL.md`. Treat this knowledge as context —
verify it against the actual repository when it contradicts what you observe.
@@ -83,16 +83,18 @@ Your primary evidence is the recurrence record and proof the safeguard fires. If
Stop when your deliverable is complete and verified per your Completion Rule; escalate when the failure mode is not understood well enough to encode safely.
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 building tools, check project memory for relevant context:
- `scripts/memory-lifecycle.sh recall failures <keywords>` — for recurring problems to prevent
- `scripts/memory-lifecycle.sh recall lessons <keywords>` — for proven automation patterns
- `scripts/memory-lifecycle.sh recall decisions <keywords>` — for tooling standards
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall failures <keywords>` — for recurring problems to prevent
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall lessons <keywords>` — for proven automation patterns
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall decisions <keywords>` — for tooling standards
After completing tooling, store durable findings:
- Recurring problem prevented → `scripts/memory-lifecycle.sh store failures <file>`
- Automation lesson learned → `scripts/memory-lifecycle.sh store lessons <file>`
- Recurring problem prevented → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store failures <file>`
- Automation lesson learned → `"${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.
Do NOT re-derive automation patterns already documented in skills.