* chore: update package-lock.json after npm install * chore: remove unused ajv-cli, keep vitest at stable 1.6.1 - Removed ajv-cli (unused dev dependency, had high severity vulnerability) - Kept vitest at 1.6.1 (stable, upgrading to v4 requires extensive refactoring) - Reduced vulnerabilities from 6 to 4 (all moderate, dev-only) - All remaining vulnerabilities are in esbuild/vite (dev server only, no production impact) - Build and tests verified working * feat(evals): add execution-balance validation to 21 OpenAgent tests and enhance agent system Major improvements to evaluation framework and agent capabilities: ## Execution Balance Evaluator Integration - Added execution-balance rule to 21 OpenAgent tests (2.7% → 31.5% coverage) - Validates "read before execute" pattern across critical rules, workflows, and edge cases - Tests now check: read operations before execution tools, healthy read/exec ratio (≥1.0) - Coverage includes: approval-gate, context-loading, stop-on-failure, report-first tests ## Agent System Enhancements - Enhanced OpenCoder agent with critical rules enforcement (approval gates, context loading) - Added structured delegation rules and workflow phases - Improved error handling with REPORT→PROPOSE→REQUEST→FIX pattern ## New Agent Creation System - Added research-backed agent creation templates and guides - Includes 8 test templates covering planning, context, incremental execution, tools - Automated agent scaffolding with /create-agent command - Complete documentation in .opencode/command/openagents/new-agents/ ## OpenCoder Test Suite - Added 8 comprehensive test cases for OpenCoder agent - Tests cover: planning, context-loading, delegation, error-handling, implementation - Includes DEBUG_GUIDE.md and QUICK_TEST_GUIDE.md for developers ## Documentation & Tooling - Added DEVELOPMENT.md guide for contributors - Enhanced CONTRIBUTING.md with quick reference and common commands - Improved event-logger with DEBUG_VERBOSE mode for detailed output - Added debug scripts: show-test-conversation.sh, run-test-verbose.sh - Removed deprecated EXTERNAL_PR_GUIDE.md ## Version Bump - Bumped version to 0.0.3 (patch) Files changed: 60+ files (21 test updates, 16 new agent templates, 8 new tests, docs, tooling) * feat(ci): add PR title validation for semantic versioning Add automated PR title validation to ensure conventional commit format. This enables proper automatic version bumping when PRs are merged. Features: - Validates PR titles against conventional commit patterns - Shows expected version bump (major/minor/patch) - Posts helpful comment with examples if validation fails - Supports all conventional commit types (feat, fix, docs, etc.) - Supports breaking changes (feat!, fix!) - Supports pre-release tags ([alpha], [beta], [rc]) When PR titles follow the format, version bumping works correctly: - feat: → minor bump (0.3.0 → 0.4.0) - fix: → patch bump (0.3.0 → 0.3.1) - feat!: → major bump (0.3.0 → 1.0.0) * fix(ci): improve PR checks workflow with sequential execution Reorganize PR checks to run in logical sequence and skip unnecessary checks: Changes: - Run PR title validation first (fast, always required) - Detect changed files to determine which checks to run - Only run build checks if evals/ files changed - Add comprehensive summary job showing all check results - Prevent cache errors when evals files not changed Benefits: - Faster PR checks (skip unnecessary builds) - Clear sequential execution (title → changes → build) - Better error messages and summaries - Reduced CI/CD costs * fix(ci): resolve PR #42 issues and refactor prompt architecture ## Fixed PR #42 Issues 1. **Prompt Validation** - Refactored to new architecture where agent files are canonical defaults 2. **Package-lock.json** - Fixed workflow to use root package-lock (npm workspaces) 3. **Git Merge Base** - Added fetch-depth: 0 to PR checks workflow ## New Prompt Architecture **Before:** - Agent files had to match .opencode/prompts/<agent>/default.md - Caused validation failures when updating prompts - Redundant duplication **After:** - Agent files (.opencode/agent/*.md) = Canonical defaults (source of truth) - Prompt variants (.opencode/prompts/<agent>/<model>.md) = Model-specific optimizations - No more default.md files needed ## Changes ### Workflows - pr-checks.yml: Added fetch-depth: 0 for full git history - validate-test-suites.yml: Fixed package-lock path for npm workspaces - validate-registry.yml: Updated validation messaging ### Scripts - validate-pr.sh: Validates prompt library structure (rejects default.md files) - use-prompt.sh: Handles 'default' as agent file, variants as model-specific - test-prompt.sh: Tests default variant correctly, saves results to prompts/results/ ### Documentation - .opencode/prompts/README.md: Updated architecture explanation - docs/contributing/CONTRIBUTING.md: Updated prompt workflow - scripts/development/demo.sh: Updated structure display ## Results - 12 files changed, 231 insertions(+), 811 deletions(-) - Net reduction: 580 lines (cleaner codebase) - All validations passing - Results directory structure preserved - Backwards compatible with existing test results |
||
|---|---|---|
| .. | ||
| openagent | ||
| opencoder | ||
| README.md | ||
Prompt Library System
Multi-model prompt variants with integrated evaluation framework for testing and validation.
🎯 Quick Start
Testing a Prompt Variant
# Test with eval framework (recommended)
cd evals/framework
npm run eval:sdk -- --agent=openagent --prompt-variant=llama --suite=smoke-test
# Test with specific model
npm run eval:sdk -- --agent=openagent --prompt-variant=llama --model=ollama/llama3.2 --suite=core-tests
# View results
open ../results/index.html
Using a Variant Permanently
# Switch to a variant
./scripts/prompts/use-prompt.sh --agent=openagent --variant=llama
# Restore default (canonical agent file)
./scripts/prompts/use-prompt.sh --agent=openagent --variant=default
📁 Structure
.opencode/
├── agent/ # Canonical agent prompts (defaults)
│ ├── openagent.md # OpenAgent default (Claude-optimized)
│ └── opencoder.md # OpenCoder default
└── prompts/ # Model-specific variants
├── README.md # This file
├── openagent/ # OpenAgent variants
│ ├── gpt.md # GPT-4 optimized
│ ├── gemini.md # Gemini optimized
│ ├── grok.md # Grok optimized
│ ├── llama.md # Llama/OSS optimized
│ ├── TEMPLATE.md # Template for new variants
│ ├── README.md # Variant documentation
│ └── results/ # Per-variant test results
│ ├── default-results.json # Default (agent file) results
│ ├── gpt-results.json
│ ├── gemini-results.json
│ └── llama-results.json
└── opencoder/ # OpenCoder variants
└── ...
Architecture:
- Agent files (
.opencode/agent/*.md) = Canonical defaults (source of truth) - Prompt variants (
.opencode/prompts/<agent>/<model>.md) = Model-specific optimizations - Results always saved to
.opencode/prompts/<agent>/results/(including default)
🧪 Evaluation Framework Integration
Running Tests with Variants
The eval framework automatically:
- ✅ Switches to the specified variant
- ✅ Runs your test suite
- ✅ Tracks results per variant
- ✅ Restores the default prompt after tests
# Smoke test (1 test, ~30s)
npm run eval:sdk -- --agent=openagent --prompt-variant=llama --suite=smoke-test
# Core suite (7 tests, ~5-8min)
npm run eval:sdk -- --agent=openagent --prompt-variant=llama --suite=core-tests
# Custom test pattern
npm run eval:sdk -- --agent=openagent --prompt-variant=llama --pattern="01-critical-rules/**/*.yaml"
Auto-Model Detection
Variants specify recommended models in their YAML frontmatter:
---
model_family: llama
recommended_models:
- ollama/llama3.2
- ollama/qwen2.5
---
If you don't specify --model, the framework uses the first recommended model.
Results Tracking
Results are saved in two locations:
- Main results:
evals/results/latest.json(includesprompt_variantfield) - Per-variant:
.opencode/prompts/{agent}/results/{variant}-results.json
View in dashboard: evals/results/index.html (filter by variant)
📝 Creating a New Variant
Step 1: Copy Template
cp .opencode/prompts/openagent/TEMPLATE.md .opencode/prompts/openagent/my-variant.md
Step 2: Edit Metadata
---
model_family: oss
recommended_models:
- ollama/my-model
status: experimental
maintainer: your-name
description: Optimized for my specific use case
---
Step 3: Customize Prompt
Edit the prompt content below the frontmatter for your target model.
Step 4: Validate
# Validate the variant exists and metadata is correct
cd evals/framework
npm run eval:sdk -- --agent=openagent --prompt-variant=my-variant --suite=smoke-test
Step 5: Test Thoroughly
# Run core test suite
npm run eval:sdk -- --agent=openagent --prompt-variant=my-variant --suite=core-tests
# Check results
open ../results/index.html
Step 6: Document Results
Update .opencode/prompts/openagent/README.md with:
- Test results (pass rate, timing)
- Known issues or limitations
- Recommended use cases
🎯 Available Variants
OpenAgent
| Variant | Model Family | Status | Best For |
|---|---|---|---|
default |
Claude | ✅ Stable | Production use, Claude models |
gpt |
GPT | ✅ Stable | GPT-4, GPT-4o |
gemini |
Gemini | ✅ Stable | Gemini 2.0, Gemini Pro |
grok |
Grok | ✅ Stable | Grok models (free tier) |
llama |
Llama/OSS | ✅ Stable | Llama, Qwen, DeepSeek, other OSS |
See openagent/README.md for detailed test results.
OpenCoder
Coming soon.
🔧 Advanced Usage
Custom Test Suites
Create custom test suites for your variant:
# Create suite
cp evals/agents/openagent/config/smoke-test.json \
evals/agents/openagent/config/my-suite.json
# Edit suite (add your tests)
# Validate suite
cd evals/framework && npm run validate:suites openagent
# Run with your variant
npm run eval:sdk -- --agent=openagent --prompt-variant=my-variant --suite=my-suite
See evals/TEST_SUITE_VALIDATION.md for details.
Comparing Models
Test the same variant with different models:
# Test Llama 3.2
npm run eval:sdk -- --agent=openagent --prompt-variant=llama --model=ollama/llama3.2 --suite=core-tests
# Test Qwen 2.5
npm run eval:sdk -- --agent=openagent --prompt-variant=llama --model=ollama/qwen2.5 --suite=core-tests
# Compare results in dashboard
open evals/results/index.html
📊 Understanding Results
Dashboard Features
The results dashboard (evals/results/index.html) shows:
- ✅ Filter by prompt variant
- ✅ Filter by model
- ✅ Pass/fail rates per variant
- ✅ Test execution times
- ✅ Detailed test results
Result Files
Main results (evals/results/latest.json):
{
"meta": {
"agent": "openagent",
"model": "ollama/llama3.2",
"prompt_variant": "llama",
"model_family": "llama"
},
"summary": {
"total": 7,
"passed": 7,
"failed": 0,
"pass_rate": 1
}
}
Per-variant results (.opencode/prompts/openagent/results/llama-results.json):
- Tracks all test runs for this variant
- Shows trends over time
- Helps identify regressions
🚀 For Contributors
Creating a Variant for PR
- Create your variant in
.opencode/prompts/<agent>/<model>.md - Test thoroughly with eval framework
- Document results in agent README
- Submit PR with variant file only
PR Requirements
- ✅ Variant has YAML frontmatter with metadata
- ✅ Variant passes core test suite (≥85% pass rate)
- ✅ Results documented in agent README
- ✅ Agent file unchanged (unless updating default)
- ✅ No
default.mdfiles in prompts directory - ✅ CI validation passes
Validation
# Validate your variant
cd evals/framework
npm run eval:sdk -- --agent=openagent --prompt-variant=your-variant --suite=core-tests
# Ensure PR uses default
./scripts/prompts/validate-pr.sh
🎓 Design Principles
1. Agent Files are Canonical Defaults
- Agent files (
.opencode/agent/*.md) are the source of truth - Tested and production-ready
- Optimized for Claude (primary model)
- Modified through normal PR process
2. Variants are Model-Specific Optimizations
- Stored in
.opencode/prompts/<agent>/<model>.md - Optimized for specific models/use cases
- May have different trade-offs
- Results documented transparently
3. Results are Tracked
- Every test run tracked per variant
- Dashboard shows variant performance
- Easy to compare variants
4. Easy to Test
- One command to test any variant
- Automatic model detection
- Results saved automatically
5. Safe to Experiment
- Variants don't affect default
- Easy to switch and restore
- Test before committing
📚 Related Documentation
- Eval Framework Guide - How to run tests
- Test Suite Validation - Creating test suites
- OpenAgent Variants - OpenAgent-specific docs
- Contributing Guide - Contribution guidelines
🆘 Troubleshooting
Variant Not Found
# List available variants
ls .opencode/prompts/openagent/*.md
# Check variant exists
npm run eval:sdk -- --agent=openagent --prompt-variant=your-variant --suite=smoke-test
Tests Failing
- Check variant metadata (YAML frontmatter)
- Verify recommended model is available
- Run with debug flag:
--debug - Check results in dashboard
Model Not Available
# Check available models
# For Ollama: ollama list
# For OpenRouter: check openrouter.ai/models
# Specify model explicitly
npm run eval:sdk -- --agent=openagent --prompt-variant=llama --model=ollama/llama3.2
💡 Tips
- Start with smoke-test - Fast validation (1 test, ~30s)
- Use core-tests for thorough testing - 7 tests, ~5-8min
- Check dashboard regularly - Visual feedback on variant performance
- Document your findings - Help others by sharing results
- Test with multiple models - Same variant may perform differently
🔮 Future Enhancements
- Automated variant comparison reports
- Performance benchmarking across variants
- Variant recommendation based on model
- Historical trend analysis
- A/B testing framework
Questions? See openagent/README.md or open an issue.