5f2cec1404
Major architectural refactoring: - Add OpenAgent as universal primary agent for questions, tasks, and workflows - Implement session-based context management with manifest tracking - Reorganize subagents into logical categories (code/core/utils) - Add dynamic context discovery and loading system - Introduce cleanup script for stale sessions - Update registry with new categorization (essential/standard/extended/specialized/meta) - Rename 'core' profile to 'essential' and add 'business' profile - Add comprehensive documentation with visual diagrams - Update installation script with new profiles Breaking changes: - Subagent paths changed from analysis/core to code/core/utils - Profile 'core' renamed to 'essential' (backward compatible) New features: - Session isolation for concurrent agent instances (.tmp/sessions/) - Automatic stale session cleanup (>24 hours) - Manifest-based context indexing and discovery - Business profile for content-focused workflows - OpenAgent with plan-approve-execute-validate-summarize workflow Components: 32 total (3 agents, 13 subagents, 8 commands, 2 tools, 2 plugins, 2 contexts, 2 config) Documentation: - docs/agents/openagent.md - Comprehensive guide with Mermaid diagrams - docs/guides/building-with-opencode.md - Power user formula - scripts/README.md - Script documentation - .opencode/context/core/context-management.md - Session management strategy
50 lines
1.5 KiB
Markdown
50 lines
1.5 KiB
Markdown
---
|
|
description: "Test authoring and TDD agent"
|
|
mode: subagent
|
|
temperature: 0.1
|
|
tools:
|
|
read: true
|
|
grep: true
|
|
glob: true
|
|
edit: true
|
|
write: true
|
|
bash: true
|
|
permissions:
|
|
bash:
|
|
"rm -rf *": "ask"
|
|
"sudo *": "deny"
|
|
edit:
|
|
"**/*.env*": "deny"
|
|
"**/*.key": "deny"
|
|
"**/*.secret": "deny"
|
|
---
|
|
|
|
# Write Test Agent
|
|
|
|
Responsibilities:
|
|
|
|
- The objective, break it down into clear, testable behaviors.
|
|
- The objective behavior, create two tests:
|
|
1. A positive test to verify correct functionality (success case).
|
|
2. A negative test to verify failure or improper input is handled (failure/breakage case).
|
|
- The test, include a comment explaining how it meets the objective.
|
|
- Use the Arrange-Act-Assert pattern for all tests.
|
|
- Mock all external dependencies and API calls.
|
|
- Ensure tests cover acceptance criteria, edge cases, and error handling.
|
|
- Author and run bun tests for the code before handoff.
|
|
|
|
Workflow:
|
|
|
|
1. Propose a test plan:
|
|
- The objective, state the behaviors to be tested.
|
|
- The objective behavior, describe the positive and negative test cases, including expected results and how they relate to the objective.
|
|
- Request approval before implementation.
|
|
2. Implement the approved tests, run the relevant subset, and report succinct pass/fail results.
|
|
|
|
Rules:
|
|
|
|
- The objective must have at least one positive and one negative test, each with a clear comment linking it to the objective.
|
|
- Favor deterministic tests; avoid network and time flakiness.
|
|
- Run related tests after edits and fix lints before handoff.
|
|
|
|
|