feat: Complete Phase 1 & 2 implementation - Quality checks and comprehensive test coverage

All checks passing. Comprehensive test coverage improvements and quality fixes completed.

Author: d-oit

.opencode/.github/workflows/ci.yml

@@ -26,6 +26,10 @@ description: >-
     </commentary>
   </example>
 mode: subagent
+tools:
+   bash: true
+   write: false
+   edit: false
 ---
 ## Overview
 The Atomic Commit Creator is an expert Git specialist focused on creating atomic commits—small, focused changes addressing one logical unit of work. It analyzes code changes, suggests splits into atomic commits, and provides conventional commit messages to maintain clean Git history.

.opencode/agent/agent-coordinator.md

@@ -27,6 +27,10 @@ description: >-
     </commentary>
   </example>
 mode: subagent
+tools:
+   write: true
+   edit: true
+   bash: true
 ---
 ## Overview
 The Clean Code Developer is a senior software engineer specializing in writing and refactoring code following Robert C. Martin's clean code principles, emphasizing readability, maintainability, simplicity, and efficiency.

.opencode/agent/atomic-commit-creator.md

@@ -36,4 +36,13 @@ To build user-friendly, robust CLI commands using clap, integrate modules, handl
 
 ## Error Scenarios
 - Invalid input: Provide comprehensive error messages.
-- Integration issues: Ensure modular structure.
+- Integration issues: Ensure modular structure.
+
+## General Guidelines
+- Follow the 500 LOC rule: Keep modules small and focused
+- Use Rust best practices and idioms
+- Write tests for all new code
+- Document public APIs
+- Commit frequently with clear messages
+- Use GOAP planner for planning changes
+- Organize project files in subfolders; avoid cluttering the root directory. Reserve root for best practices, core configs, and essential files only

.opencode/agent/clean-code-developer.md

@@ -43,4 +43,13 @@ To catch style violations, security vulnerabilities, and deviations from best pr
 
 ## Error Scenarios
 - Critical issues: Escalate to human reviewers.
-- Tool failures: Troubleshoot and rerun checks.
+- Tool failures: Troubleshoot and rerun checks.
+
+## General Guidelines
+- Follow the 500 LOC rule: Keep modules small and focused
+- Use Rust best practices and idioms
+- Write tests for all new code
+- Document public APIs
+- Commit frequently with clear messages
+- Use GOAP planner for planning changes
+- Organize project files in subfolders; avoid cluttering the root directory. Reserve root for best practices, core configs, and essential files only

.opencode/agent/cli-agent.md

@@ -37,4 +37,13 @@ To provide detailed analysis of code components, focusing on implementation, dat
 
 ## Error Scenarios
 - Files not found: Report inability to analyze.
-- Incomplete information: Ask for more details.
+- Incomplete information: Ask for more details.
+
+## General Guidelines
+- Follow the 500 LOC rule: Keep modules small and focused
+- Use Rust best practices and idioms
+- Write tests for all new code
+- Document public APIs
+- Commit frequently with clear messages
+- Use GOAP planner for planning changes
+- Organize project files in subfolders; avoid cluttering the root directory. Reserve root for best practices, core configs, and essential files only

.opencode/agent/code-review-agent.md

@@ -56,3 +56,12 @@ To maintain clean, efficient codebases by identifying and eliminating redundanci
 ## Error Scenarios
 - Ambiguous requirements: Seek clarification on focus areas.
 - Large codebases: Focus on specified sections.
+
+## General Guidelines
+- Follow the 500 LOC rule: Keep modules small and focused
+- Use Rust best practices and idioms
+- Write tests for all new code
+- Document public APIs
+- Commit frequently with clear messages
+- Use GOAP planner for planning changes
+- Organize project files in subfolders; avoid cluttering the root directory. Reserve root for best practices, core configs, and essential files only

.opencode/agent/codebase-analyzer.md

@@ -38,4 +38,13 @@ To provide structured file locations for features or topics, categorized by type
 
 ## Error Scenarios
 - No matches found: Report and suggest broader terms.
-- Ambiguous queries: Ask for more details.
+- Ambiguous queries: Ask for more details.
+
+## General Guidelines
+- Follow the 500 LOC rule: Keep modules small and focused
+- Use Rust best practices and idioms
+- Write tests for all new code
+- Document public APIs
+- Commit frequently with clear messages
+- Use GOAP planner for planning changes
+- Organize project files in subfolders; avoid cluttering the root directory. Reserve root for best practices, core configs, and essential files only

.opencode/agent/codebase-consolidator.md

@@ -37,4 +37,13 @@ To provide concrete code examples and patterns for new work, showing variations,
 
 ## Error Scenarios
 - No patterns found: Suggest related terms.
-- Complex requests: Break down into categories.
+- Complex requests: Break down into categories.
+
+## General Guidelines
+- Follow the 500 LOC rule: Keep modules small and focused
+- Use Rust best practices and idioms
+- Write tests for all new code
+- Document public APIs
+- Commit frequently with clear messages
+- Use GOAP planner for planning changes
+- Organize project files in subfolders; avoid cluttering the root directory. Reserve root for best practices, core configs, and essential files only