skynet/agent-runtime-framework
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(harness): align workspace paths and best-practices mount target

Browse Source 
- Mount best-practices context at /workspace/best-practices/ (was
  /opt/harness/context/best-practices/) for consistent agent access
- Fix /workspace/working/ → /workspace/project/ in all CLAUDE.md files
  (planning, spec-writing, security-review, code-methodology,
  qwen-code-methodology, test-writing)
- Update best-practices path references in all CLAUDE.md files to
  /workspace/best-practices/

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Paul O'Reilly
2026-04-28 13:24:10 +12:00
parent b04f718530
commit c0758cbd71
7 changed files with 26 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
harnesses/contexts/code-methodology/v1/CLAUDE.md
View File

@@ -4,21 +4,21 @@
Before starting any task:
1. Check if `/best-practices/INDEX.md` exists
1. Check if `/workspace/best-practices/INDEX.md` exists
2. If it exists, read it to see available topics
3. Identify relevant topics for the current task:
- Python task → read `test-driven-development.md`, `spec-driven-development.md`
- Kubernetes task → read `kubernetes.md`
- Shell scripts → read `scripting.md`
4. Read the relevant topic files from `/best-practices/`
4. Read the relevant topic files from `/workspace/best-practices/`
5. Apply those practices to your work
If `/best-practices/` doesn't exist, proceed without — it's not mandatory.
If `/workspace/best-practices/` doesn't exist, proceed without — it's not mandatory.
## Spec-Driven Development Workflow
1. **Read the spec** — Read relevant files in `spec/` before writing any code
2. **Write tests first** — Create test cases from spec requirements before implementing (see `best-practices/test-driven-development.md` and `best-practices/spec-driven-development.md` if available)
2. **Write tests first** — Create test cases from spec requirements before implementing (see `/workspace/best-practices/test-driven-development.md` and `/workspace/best-practices/spec-driven-development.md` if available)
3. **Implement iteratively** — Build implementation to satisfy tests and spec
4. **Write session log** — Document what was accomplished, decisions made, and gotchas discovered