OpenAgentsControl/.opencode/command/commit-openagents.md

---

description: Smart commit command for opencode-agents repository with automatic validation and conventional commits

Commit OpenAgents Command

You are an AI agent that helps create well-formatted git commits specifically for the opencode-agents repository. This command handles the complete commit workflow including validation, testing, and pushing changes.

Instructions for Agent

When the user runs this command, execute the following workflow:

1. Pre-Commit Validation (Optional)

Ask user first:

Would you like to run smoke tests before committing? (y/n)
- y: Run validation tests
- n: Skip directly to commit

If user chooses to run tests:

cd evals/framework && npm run eval:sdk -- --agent=core/openagent --pattern="**/smoke-test.yaml"
cd evals/framework && npm run eval:sdk -- --agent=core/opencoder --pattern="**/smoke-test.yaml"

Validation Rules:

• ⚠️ If tests fail, ask user if they want to proceed or fix issues first
• ✅ Tests are optional - user can skip and commit directly

2. Analyze Changes

• Run git status to see all untracked files
• Run git diff to see both staged and unstaged changes
• Run git log --oneline -5 to see recent commit style
• Identify the scope of changes (evals, scripts, docs, agents, etc.)

3. Stage Files Intelligently

Auto-stage based on change type:

• If modifying evals framework → stage evals/framework/
• If modifying core agents → stage .opencode/agent/core/
• If modifying development agents → stage .opencode/agent/development/
• If modifying content agents → stage .opencode/agent/content/
• If modifying data agents → stage .opencode/agent/data/
• If modifying meta agents → stage .opencode/agent/meta/
• If modifying learning agents → stage .opencode/agent/learning/
• If modifying product agents → stage .opencode/agent/product/
• If modifying subagents → stage .opencode/agent/subagents/
• If modifying commands → stage .opencode/command/
• If modifying context → stage .opencode/context/
• If modifying scripts → stage scripts/
• If modifying docs → stage docs/
• If modifying CI/CD → stage .github/workflows/
• If user provides specific files → stage only those

Never auto-stage:

• node_modules/
• .env files
• test_tmp/ or temporary directories
• evals/results/ (test results)

4. Generate Commit Message

Follow Conventional Commits (NO EMOJIS):

<type>(<scope>): <description>

[optional body]

Types for this repo:

• feat - New features (agents, commands, tools)
• fix - Bug fixes
• refactor - Code restructuring without behavior change
• test - Test additions or modifications
• docs - Documentation updates
• chore - Maintenance tasks (dependencies, cleanup)
• ci - CI/CD pipeline changes
• perf - Performance improvements

Scopes for this repo:

• evals - Evaluation framework changes
• agents/core - Core agents (openagent, opencoder)
• agents/meta - Meta agents (system-builder, repo-manager)
• agents/development - Development category agents (frontend-specialist, backend-specialist, devops-specialist, codebase-agent)
• agents/content - Content category agents (copywriter, technical-writer)
• agents/data - Data category agents (data-analyst)
• agents/learning - Learning category agents
• agents/product - Product category agents
• subagents/core - Core subagents (task-manager, documentation, context-retriever)
• subagents/code - Code subagents (coder-agent, tester, reviewer, build-agent, codebase-pattern-analyst)
• subagents/system-builder - System builder subagents (domain-analyzer, agent-generator, context-organizer, workflow-designer, command-creator)
• subagents/utils - Utility subagents (image-specialist)
• commands - Slash command changes
• context - Context file changes
• scripts - Build/test script changes
• ci - GitHub Actions workflow changes
• docs - Documentation changes
• registry - Registry.json changes

Examples:

feat(evals): add parallel test execution support
fix(agents/core): correct delegation logic in openagent
fix(agents/development): update frontend-specialist validation rules
feat(agents/content): add new copywriter capabilities
feat(agents/meta): enhance system-builder with new templates
refactor(evals): split test-runner into modular components
test(evals): add smoke tests for openagent
feat(subagents/code): add build validation to build-agent
feat(subagents/system-builder): improve domain-analyzer pattern detection
docs(readme): update installation instructions
chore(deps): upgrade evaluation framework dependencies
feat(registry): add new agent categories
ci: add automatic version bumping workflow

5. Commit Analysis

• List all files that have been changed or added
• Summarize the nature of changes (new feature, bug fix, refactor, etc.)
• Identify the primary scope (evals, agents, scripts, etc.)
• Determine the purpose/motivation behind changes
• Assess impact on the overall project
• Check for sensitive information (API keys, tokens, etc.)
• Draft a concise commit message focusing on "why" not "what"
• Ensure message follows conventional commit format
• Verify message is specific and not generic

6. Execute Commit

git add <relevant-files>
git commit -m "<type>(<scope>): <description>"
git status  # Verify commit succeeded

7. Post-Commit Actions

Ask user:

✅ Commit created: <commit-hash>
📝 Message: <commit-message>

Would you like to:
1. Push to remote (git push origin main)
2. Create another commit
3. Done

If user chooses push:

git push origin main

Then inform:

🚀 Pushed to remote!

This will trigger:
- GitHub Actions CI/CD workflow
- Smoke tests for openagent & opencoder
- Automatic version bumping (if feat/fix commit)
- CHANGELOG.md update

Repository-Specific Rules

Version Bumping (Automatic via CI/CD)

Commits trigger automatic version bumps:

• feat: → minor bump (0.0.1 → 0.1.0)
• fix: → patch bump (0.0.1 → 0.0.2)
• feat!: or BREAKING CHANGE: → major bump (0.1.0 → 1.0.0)
• [alpha] in message → alpha bump (0.1.0-alpha.1 → 0.1.0-alpha.2)
• Default → patch bump (0.0.1 → 0.0.2)

Files to Always Check

Before committing, verify these are in sync:

• VERSION file
• package.json version
• CHANGELOG.md (if manually updated)

Pre-Commit Hooks

This repo may have pre-commit hooks that:

• Run linting
• Format code
• Run type checks

If hooks modify files:

• Automatically amend the commit to include hook changes
• Inform user that files were auto-formatted

Error Handling

If Smoke Tests Fail

⚠️ Smoke tests failed for <agent-name>

Failures:
<test-output>

Options:
1. Fix issues and retry
2. Run full test suite (cd evals/framework && npm run eval:sdk -- --agent=<category>/<agent>)
3. Proceed anyway (not recommended)
4. Cancel commit

What would you like to do?

If No Changes Detected

ℹ️ No changes to commit. Working tree is clean.

Recent commits:
<git log --oneline -3>

Would you like to:
1. Check git status
2. View recent commits
3. Exit

If Merge Conflicts

⚠️ Merge conflicts detected. Please resolve conflicts first.

Conflicted files:
<list-files>

Run: git status

Agent Behavior Notes

• Optional validation - Ask user if they want to run smoke tests (not mandatory)
• Smart staging - Only stage relevant files based on change scope and category structure
• Conventional commits - Strictly follow conventional commit format (NO EMOJIS)
• Scope awareness - Use appropriate scope for this repository (include category paths)
• Version awareness - Inform user about automatic version bumping
• CI/CD awareness - Remind user that push triggers automated workflows
• Security - Never commit sensitive information (API keys, tokens, .env files)
• Atomic commits - Each commit should have a single, clear purpose
• Push guidance - Always ask before pushing to remote
• Category-aware - Recognize new agent organization (core, development, content, data, meta, learning, product)

Quick Reference

Common Workflows

Feature Addition:

# 1. Optional: Run smoke tests
cd evals/framework && npm run eval:sdk -- --agent=core/openagent --pattern="**/smoke-test.yaml"

# 2. Stage and commit
git add <files>
git commit -m "feat(evals): add new evaluation metric"

# 3. Push
git push origin main

Bug Fix:

git add <files>
git commit -m "fix(agents/core): correct delegation threshold logic"
git push origin main

Documentation:

git add docs/
git commit -m "docs(guides): update testing documentation"
git push origin main

Refactoring:

git add evals/framework/src/
git commit -m "refactor(evals): extract validation logic into separate module"
git push origin main

Success Criteria

A successful commit should:

• ✅ Follow conventional commit format (NO EMOJIS)
• ✅ Have appropriate scope with category path (e.g., agents/core, subagents/code)
• ✅ Be atomic (single purpose)
• ✅ Have clear, concise message
• ✅ Not include sensitive information
• ✅ Not include generated files (node_modules, build artifacts)
• ✅ Only stage relevant files based on category structure
• ✅ Trigger appropriate CI/CD workflows when pushed
• ✅ Optionally pass smoke tests if validation was requested