Merge branch 'develop'

Author: d-oit

.opencode/agent/command-interpreter.md

@@ -0,0 +1,46 @@
+---
+description: >-
+  Use this agent when the user provides a command or instruction that requires
+  interpretation, execution, or delegation within the project context, such as
+  running scripts, issuing directives, or handling procedural requests. Examples
+  include:
+
+
+  <example>
+    Context: The user is requesting to run a specific command in the development environment.
+    user: "Run the build command for the Rust project"
+    assistant: "I'm going to use the Task tool to launch the command-interpreter agent to handle the build command execution"
+    <commentary>
+    Since the user is issuing a command to run a build, use the command-interpreter agent to interpret and execute the appropriate build process. 
+    </commentary>
+  </example>
+
+
+  <example>
+    Context: The user is giving a procedural instruction that needs to be broken down and acted upon.
+    user: "Update the dependencies and then test the application"
+    assistant: "Now let me use the Task tool to launch the command-interpreter agent to sequentially update dependencies and run tests"
+    <commentary>
+    Since the user is providing a multi-step command, use the command-interpreter agent to parse and execute the steps in order. 
+    </commentary>
+  </example>
+mode: subagent
+---
+You are a Command Interpreter Agent, an expert in parsing, validating, and executing user commands within the project's development environment. Your primary role is to interpret commands issued by users, ensure they align with project standards and safety protocols, and execute them efficiently while providing clear feedback.
+
+You will:
+- Parse the user's command to identify the intent, required actions, and any parameters.
+- Validate the command against project-specific rules from AGENTS.md files, ensuring compliance with coding standards, security guidelines, and operational boundaries.
+- Execute the command using appropriate tools or methods, such as running scripts, invoking APIs, or delegating to other agents if needed.
+- Handle errors gracefully by providing diagnostic information and suggesting corrective actions.
+- Maintain a log of executed commands for traceability and avoid redundant operations.
+- Seek clarification from the user if the command is ambiguous, incomplete, or potentially harmful.
+- Prioritize safety: Never execute commands that could compromise security, data integrity, or violate legal/ethical standards.
+- For multi-step commands, break them down into sequential tasks and execute them in order, reporting progress at each step.
+- If a command requires external resources or permissions not available, escalate by requesting user intervention or suggesting alternatives.
+- Output results in a structured format: Start with a summary of the command, followed by execution status, any outputs or errors, and next steps.
+- Incorporate best practices from project context, such as using specific tools for Rust development if applicable.
+- Self-verify execution by checking for expected outcomes and confirming success criteria.
+- If execution fails, attempt one retry with adjustments, then provide detailed failure analysis.
+
+Always operate proactively: If a command implies dependencies (e.g., needing to install something first), address them automatically where possible. Your goal is to make command execution seamless and reliable, enhancing productivity without introducing risks.

.opencode/command/release.md

@@ -17,7 +17,7 @@ To ensure releases are built, tested, and deployed reliably, coordinating multip
 
 ## Dependencies
 - Cargo toolchain.
-- Agents: CI Agent, Storage Agent, Docs Agent, Git Handler, Hive Mind Orchestrator.
+- Agents: CI Agent, Storage Agent, Docs Agent, Git Handler, GitHub, Hive Mind Orchestrator.
 
 ## Usage Examples
 - Standard release: `/release`
@@ -38,8 +38,8 @@ To ensure releases are built, tested, and deployed reliably, coordinating multip
 - **Network/Permission Issues**: For pushing tags, ensure auth and connectivity.
 
 ## Integration Notes
-- **Handoff Protocols**: Sequential handoffs: checks -> version bump -> CI -> storage update -> docs -> git. Confirm each step before proceeding.
-- **Collaboration**: Uses CI Agent for pipelines, Storage for versions, Docs for updates, Git for commits/tags. For complex releases, hand off to Hive Mind Orchestrator.
+- **Handoff Protocols**: Sequential handoffs: checks -> version bump -> CI -> storage update -> docs -> git -> github (PR creation and merge). Confirm each step before proceeding.
+- **Collaboration**: Uses CI Agent for pipelines, Storage for versions, Docs for updates, Git for commits/tags, GitHub for PR creation and merging. For complex releases, hand off to Hive Mind Orchestrator.
 - **Best Practices**: Always run checks first; log all actions. Confirm completion with user.
 - **Edge Cases**: Handle pre-releases differently; for hotfixes, skip some checks if urgent (with caution).
 
@@ -59,12 +59,26 @@ If clippy finds issues, stop and report warnings/errors.
 Format check: !`cargo fmt --check`
 If formatting issues, stop and report.
 
+Doc tests: !`cargo test --doc`
+If doc tests fail, stop and report failures.
+
+Coverage generation: !`cargo llvm-cov --all-features --workspace --lcov --output-path lcov.info`
+If coverage generation fails, stop and report errors.
+
+Security audit: !`cargo audit`
+If security vulnerabilities are found, stop and report.
+
 If all checks pass:
 1. Determine new version: /version-bump $ARGUMENTS
 2. @ci-agent to handle CI/CD pipeline.
 3. Update version in Cargo.toml using @storage-agent.
 4. @docs-agent to update changelog/docs.
 5. @git-handler for tagging and pushing.
-6. If needed, @hive-mind-orchestrator for complex releases.
+6. @github agent to create a pull request from the current branch (e.g., develop) to main.
+7. @github agent to merge the pull request.
+8. Switch to develop branch and merge main back into it to sync changes.
+9. If needed, @hive-mind-orchestrator for complex releases.
+
+10. @github agent to monitor the GitHub Actions workflows (CI, Deploy Docs, Release) to ensure they complete successfully.
 
 Confirm release completion.

CHANGELOG.md

@@ -5,6 +5,31 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+### Added
+- **🌍 Multi-Language Non-Production Code Detection**: Added 13 new detectors for finding non-production code across 30+ programming languages
+  - **Development/Phase Patterns**: `Dev`, `Debug`, `Test`, `Phase`, `Staging` 
+  - **Non-Production Code**: `ConsoleLog`, `Print`, `Alert`, `Debugger`, `UnusedVar`, `DeadCode`, `Experimental`
+- **🎯 Production-Ready Detector Profile**: New comprehensive profile specifically for production readiness scanning
+- **📱 Language-Specific Detection**: Smart filtering (e.g., console.log only detected in JS/TS files, alerts in web files)
+- **⚙️ Enhanced Multi-Language Support**: Extended support for 30+ file extensions including TypeScript, Python, C#, Go, PHP, Java, Kotlin, Swift, Dart, Scala, and more
+- **📋 Production Configuration Template**: Complete `examples/production_ready_config.toml` with severity levels and custom patterns
+- **📖 Comprehensive Documentation**: Detailed `examples/production_ready_scan_demo.md` with usage guides for multi-language scanning
+- **✅ Comprehensive Test Coverage**: Integration tests demonstrating multi-language detection across JavaScript, TypeScript, Python, Rust, and Go
+
+### Enhanced
+- **🔧 Extended DetectorType Enum**: Added 13 new detector types with appropriate severity levels (Critical, High, Medium, Low)
+- **🏭 Enhanced DetectorFactory**: New `create_production_ready_detectors()` method and `ProductionReady` profile
+- **📁 Expanded File Support**: Default configuration now includes 30+ file extensions for comprehensive language coverage
+- **🎨 Improved Regex Patterns**: Optimized detection patterns for better accuracy across different programming languages
+
+### Technical Improvements
+- All new detectors follow Rust best practices with comprehensive error handling
+- Language-specific filtering prevents false positives (e.g., console.log not detected in Python files)
+- Smart test file exclusion (TestDetector skips actual test directories)
+- Backward compatible - no breaking changes to existing API
+
 ## [0.1.0-alpha] - 2025-10-06
 
 ### Added

Cargo.lock

@@ -1,5 +1,5 @@
 [package]
-name = "code-guardian-cli"
+name = "code_guardian_cli"
 version = "0.1.0-alpha"
 edition = "2021"