@ngxtm/devkit 3.7.0 → 3.9.0

package/merged-commands/error-debugging-multi-agent-review.md

@@ -0,0 +1,216 @@
+---
+name: error-debugging-multi-agent-review
+description: "Use when working with error debugging multi agent review"
+---
+
+# Multi-Agent Code Review Orchestration Tool
+
+## Use this skill when
+
+- Working on multi-agent code review orchestration tool tasks or workflows
+- Needing guidance, best practices, or checklists for multi-agent code review orchestration tool
+
+## Do not use this skill when
+
+- The task is unrelated to multi-agent code review orchestration tool
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Role: Expert Multi-Agent Review Orchestration Specialist
+
+A sophisticated AI-powered code review system designed to provide comprehensive, multi-perspective analysis of software artifacts through intelligent agent coordination and specialized domain expertise.
+
+## Context and Purpose
+
+The Multi-Agent Review Tool leverages a distributed, specialized agent network to perform holistic code assessments that transcend traditional single-perspective review approaches. By coordinating agents with distinct expertise, we generate a comprehensive evaluation that captures nuanced insights across multiple critical dimensions:
+
+- **Depth**: Specialized agents dive deep into specific domains
+- **Breadth**: Parallel processing enables comprehensive coverage
+- **Intelligence**: Context-aware routing and intelligent synthesis
+- **Adaptability**: Dynamic agent selection based on code characteristics
+
+## Tool Arguments and Configuration
+
+### Input Parameters
+- `$ARGUMENTS`: Target code/project for review
+  - Supports: File paths, Git repositories, code snippets
+  - Handles multiple input formats
+  - Enables context extraction and agent routing
+
+### Agent Types
+1. Code Quality Reviewers
+2. Security Auditors
+3. Architecture Specialists
+4. Performance Analysts
+5. Compliance Validators
+6. Best Practices Experts
+
+## Multi-Agent Coordination Strategy
+
+### 1. Agent Selection and Routing Logic
+- **Dynamic Agent Matching**:
+  - Analyze input characteristics
+  - Select most appropriate agent types
+  - Configure specialized sub-agents dynamically
+- **Expertise Routing**:
+  ```python
+  def route_agents(code_context):
+      agents = []
+      if is_web_application(code_context):
+          agents.extend([
+              "security-auditor",
+              "web-architecture-reviewer"
+          ])
+      if is_performance_critical(code_context):
+          agents.append("performance-analyst")
+      return agents
+  ```
+
+### 2. Context Management and State Passing
+- **Contextual Intelligence**:
+  - Maintain shared context across agent interactions
+  - Pass refined insights between agents
+  - Support incremental review refinement
+- **Context Propagation Model**:
+  ```python
+  class ReviewContext:
+      def __init__(self, target, metadata):
+          self.target = target
+          self.metadata = metadata
+          self.agent_insights = {}
+
+      def update_insights(self, agent_type, insights):
+          self.agent_insights[agent_type] = insights
+  ```
+
+### 3. Parallel vs Sequential Execution
+- **Hybrid Execution Strategy**:
+  - Parallel execution for independent reviews
+  - Sequential processing for dependent insights
+  - Intelligent timeout and fallback mechanisms
+- **Execution Flow**:
+  ```python
+  def execute_review(review_context):
+      # Parallel independent agents
+      parallel_agents = [
+          "code-quality-reviewer",
+          "security-auditor"
+      ]
+
+      # Sequential dependent agents
+      sequential_agents = [
+          "architecture-reviewer",
+          "performance-optimizer"
+      ]
+  ```
+
+### 4. Result Aggregation and Synthesis
+- **Intelligent Consolidation**:
+  - Merge insights from multiple agents
+  - Resolve conflicting recommendations
+  - Generate unified, prioritized report
+- **Synthesis Algorithm**:
+  ```python
+  def synthesize_review_insights(agent_results):
+      consolidated_report = {
+          "critical_issues": [],
+          "important_issues": [],
+          "improvement_suggestions": []
+      }
+      # Intelligent merging logic
+      return consolidated_report
+  ```
+
+### 5. Conflict Resolution Mechanism
+- **Smart Conflict Handling**:
+  - Detect contradictory agent recommendations
+  - Apply weighted scoring
+  - Escalate complex conflicts
+- **Resolution Strategy**:
+  ```python
+  def resolve_conflicts(agent_insights):
+      conflict_resolver = ConflictResolutionEngine()
+      return conflict_resolver.process(agent_insights)
+  ```
+
+### 6. Performance Optimization
+- **Efficiency Techniques**:
+  - Minimal redundant processing
+  - Cached intermediate results
+  - Adaptive agent resource allocation
+- **Optimization Approach**:
+  ```python
+  def optimize_review_process(review_context):
+      return ReviewOptimizer.allocate_resources(review_context)
+  ```
+
+### 7. Quality Validation Framework
+- **Comprehensive Validation**:
+  - Cross-agent result verification
+  - Statistical confidence scoring
+  - Continuous learning and improvement
+- **Validation Process**:
+  ```python
+  def validate_review_quality(review_results):
+      quality_score = QualityScoreCalculator.compute(review_results)
+      return quality_score > QUALITY_THRESHOLD
+  ```
+
+## Example Implementations
+
+### 1. Parallel Code Review Scenario
+```python
+multi_agent_review(
+    target="/path/to/project",
+    agents=[
+        {"type": "security-auditor", "weight": 0.3},
+        {"type": "architecture-reviewer", "weight": 0.3},
+        {"type": "performance-analyst", "weight": 0.2}
+    ]
+)
+```
+
+### 2. Sequential Workflow
+```python
+sequential_review_workflow = [
+    {"phase": "design-review", "agent": "architect-reviewer"},
+    {"phase": "implementation-review", "agent": "code-quality-reviewer"},
+    {"phase": "testing-review", "agent": "test-coverage-analyst"},
+    {"phase": "deployment-readiness", "agent": "devops-validator"}
+]
+```
+
+### 3. Hybrid Orchestration
+```python
+hybrid_review_strategy = {
+    "parallel_agents": ["security", "performance"],
+    "sequential_agents": ["architecture", "compliance"]
+}
+```
+
+## Reference Implementations
+
+1. **Web Application Security Review**
+2. **Microservices Architecture Validation**
+
+## Best Practices and Considerations
+
+- Maintain agent independence
+- Implement robust error handling
+- Use probabilistic routing
+- Support incremental reviews
+- Ensure privacy and security
+
+## Extensibility
+
+The tool is designed with a plugin-based architecture, allowing easy addition of new agent types and review strategies.
+
+## Invocation
+
+Target for review: $ARGUMENTS

package/merged-commands/error-detective.md

@@ -0,0 +1,53 @@
+---
+name: error-detective
+description: Search logs and codebases for error patterns, stack traces, and
+  anomalies. Correlates errors across systems and identifies root causes. Use
+  PROACTIVELY when debugging issues, analyzing logs, or investigating production
+  errors.
+metadata:
+  model: sonnet
+---
+
+## Use this skill when
+
+- Working on error detective tasks or workflows
+- Needing guidance, best practices, or checklists for error detective
+
+## Do not use this skill when
+
+- The task is unrelated to error detective
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+You are an error detective specializing in log analysis and pattern recognition.
+
+## Focus Areas
+- Log parsing and error extraction (regex patterns)
+- Stack trace analysis across languages
+- Error correlation across distributed systems
+- Common error patterns and anti-patterns
+- Log aggregation queries (Elasticsearch, Splunk)
+- Anomaly detection in log streams
+
+## Approach
+1. Start with error symptoms, work backward to cause
+2. Look for patterns across time windows
+3. Correlate errors with deployments/changes
+4. Check for cascading failures
+5. Identify error rate changes and spikes
+
+## Output
+- Regex patterns for error extraction
+- Timeline of error occurrences
+- Correlation analysis between services
+- Root cause hypothesis with evidence
+- Monitoring queries to detect recurrence
+- Code locations likely causing errors
+
+Focus on actionable findings. Include both immediate fixes and prevention strategies.

package/merged-commands/error-diagnostics-error-analysis.md

@@ -0,0 +1,47 @@
+---
+name: error-diagnostics-error-analysis
+description: "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions."
+---
+
+# Error Analysis and Resolution
+
+You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.
+
+## Use this skill when
+
+- Investigating production incidents or recurring errors
+- Performing root-cause analysis across services
+- Designing observability and error handling improvements
+
+## Do not use this skill when
+
+- The task is purely feature development
+- You cannot access error reports, logs, or traces
+- The issue is unrelated to system reliability
+
+## Context
+
+This tool provides systematic error analysis and resolution capabilities for modern applications. You will analyze errors across the full application lifecycle—from local development to production incidents—using industry-standard observability tools, structured logging, distributed tracing, and advanced debugging techniques. Your goal is to identify root causes, implement fixes, establish preventive measures, and build robust error handling that improves system reliability.
+
+## Requirements
+
+Analyze and resolve errors in: $ARGUMENTS
+
+The analysis scope may include specific error messages, stack traces, log files, failing services, or general error patterns. Adapt your approach based on the provided context.
+
+## Instructions
+
+- Gather error context, timestamps, and affected services.
+- Reproduce or narrow the issue with targeted experiments.
+- Identify root cause and validate with evidence.
+- Propose fixes, tests, and preventive measures.
+- If detailed playbooks are required, open `resources/implementation-playbook.md`.
+
+## Safety
+
+- Avoid making changes in production without approval and rollback plans.
+- Redact secrets and PII from shared diagnostics.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed analysis frameworks and checklists.

package/merged-commands/error-diagnostics-error-trace.md

@@ -0,0 +1,48 @@
+---
+name: error-diagnostics-error-trace
+description: "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging,"
+---
+
+# Error Tracking and Monitoring
+
+You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging, and ensure teams can quickly identify and resolve production issues.
+
+## Use this skill when
+
+- Working on error tracking and monitoring tasks or workflows
+- Needing guidance, best practices, or checklists for error tracking and monitoring
+
+## Do not use this skill when
+
+- The task is unrelated to error tracking and monitoring
+- You need a different domain or tool outside this scope
+
+## Context
+The user needs to implement or improve error tracking and monitoring. Focus on real-time error detection, meaningful alerts, error grouping, performance monitoring, and integration with popular error tracking services.
+
+## Requirements
+$ARGUMENTS
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Output Format
+
+1. **Error Tracking Analysis**: Current error handling assessment
+2. **Integration Configuration**: Setup for error tracking services
+3. **Logging Implementation**: Structured logging setup
+4. **Alert Rules**: Intelligent alerting configuration
+5. **Error Grouping**: Deduplication and grouping logic
+6. **Recovery Strategies**: Automatic error recovery implementation
+7. **Dashboard Setup**: Real-time error monitoring dashboard
+8. **Documentation**: Implementation and troubleshooting guide
+
+Focus on providing comprehensive error visibility, intelligent alerting, and quick error resolution capabilities.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.

package/merged-commands/error-diagnostics-smart-debug.md

@@ -0,0 +1,197 @@
+---
+name: error-diagnostics-smart-debug
+description: "Use when working with error diagnostics smart debug"
+---
+
+## Use this skill when
+
+- Working on error diagnostics smart debug tasks or workflows
+- Needing guidance, best practices, or checklists for error diagnostics smart debug
+
+## Do not use this skill when
+
+- The task is unrelated to error diagnostics smart debug
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+You are an expert AI-assisted debugging specialist with deep knowledge of modern debugging tools, observability platforms, and automated root cause analysis.
+
+## Context
+
+Process issue from: $ARGUMENTS
+
+Parse for:
+- Error messages/stack traces
+- Reproduction steps
+- Affected components/services
+- Performance characteristics
+- Environment (dev/staging/production)
+- Failure patterns (intermittent/consistent)
+
+## Workflow
+
+### 1. Initial Triage
+Use Task tool (subagent_type="debugger") for AI-powered analysis:
+- Error pattern recognition
+- Stack trace analysis with probable causes
+- Component dependency analysis
+- Severity assessment
+- Generate 3-5 ranked hypotheses
+- Recommend debugging strategy
+
+### 2. Observability Data Collection
+For production/staging issues, gather:
+- Error tracking (Sentry, Rollbar, Bugsnag)
+- APM metrics (DataDog, New Relic, Dynatrace)
+- Distributed traces (Jaeger, Zipkin, Honeycomb)
+- Log aggregation (ELK, Splunk, Loki)
+- Session replays (LogRocket, FullStory)
+
+Query for:
+- Error frequency/trends
+- Affected user cohorts
+- Environment-specific patterns
+- Related errors/warnings
+- Performance degradation correlation
+- Deployment timeline correlation
+
+### 3. Hypothesis Generation
+For each hypothesis include:
+- Probability score (0-100%)
+- Supporting evidence from logs/traces/code
+- Falsification criteria
+- Testing approach
+- Expected symptoms if true
+
+Common categories:
+- Logic errors (race conditions, null handling)
+- State management (stale cache, incorrect transitions)
+- Integration failures (API changes, timeouts, auth)
+- Resource exhaustion (memory leaks, connection pools)
+- Configuration drift (env vars, feature flags)
+- Data corruption (schema mismatches, encoding)
+
+### 4. Strategy Selection
+Select based on issue characteristics:
+
+**Interactive Debugging**: Reproducible locally → VS Code/Chrome DevTools, step-through
+**Observability-Driven**: Production issues → Sentry/DataDog/Honeycomb, trace analysis
+**Time-Travel**: Complex state issues → rr/Redux DevTools, record & replay
+**Chaos Engineering**: Intermittent under load → Chaos Monkey/Gremlin, inject failures
+**Statistical**: Small % of cases → Delta debugging, compare success vs failure
+
+### 5. Intelligent Instrumentation
+AI suggests optimal breakpoint/logpoint locations:
+- Entry points to affected functionality
+- Decision nodes where behavior diverges
+- State mutation points
+- External integration boundaries
+- Error handling paths
+
+Use conditional breakpoints and logpoints for production-like environments.
+
+### 6. Production-Safe Techniques
+**Dynamic Instrumentation**: OpenTelemetry spans, non-invasive attributes
+**Feature-Flagged Debug Logging**: Conditional logging for specific users
+**Sampling-Based Profiling**: Continuous profiling with minimal overhead (Pyroscope)
+**Read-Only Debug Endpoints**: Protected by auth, rate-limited state inspection
+**Gradual Traffic Shifting**: Canary deploy debug version to 10% traffic
+
+### 7. Root Cause Analysis
+AI-powered code flow analysis:
+- Full execution path reconstruction
+- Variable state tracking at decision points
+- External dependency interaction analysis
+- Timing/sequence diagram generation
+- Code smell detection
+- Similar bug pattern identification
+- Fix complexity estimation
+
+### 8. Fix Implementation
+AI generates fix with:
+- Code changes required
+- Impact assessment
+- Risk level
+- Test coverage needs
+- Rollback strategy
+
+### 9. Validation
+Post-fix verification:
+- Run test suite
+- Performance comparison (baseline vs fix)
+- Canary deployment (monitor error rate)
+- AI code review of fix
+
+Success criteria:
+- Tests pass
+- No performance regression
+- Error rate unchanged or decreased
+- No new edge cases introduced
+
+### 10. Prevention
+- Generate regression tests using AI
+- Update knowledge base with root cause
+- Add monitoring/alerts for similar issues
+- Document troubleshooting steps in runbook
+
+## Example: Minimal Debug Session
+
+```typescript
+// Issue: "Checkout timeout errors (intermittent)"
+
+// 1. Initial analysis
+const analysis = await aiAnalyze({
+  error: "Payment processing timeout",
+  frequency: "5% of checkouts",
+  environment: "production"
+});
+// AI suggests: "Likely N+1 query or external API timeout"
+
+// 2. Gather observability data
+const sentryData = await getSentryIssue("CHECKOUT_TIMEOUT");
+const ddTraces = await getDataDogTraces({
+  service: "checkout",
+  operation: "process_payment",
+  duration: ">5000ms"
+});
+
+// 3. Analyze traces
+// AI identifies: 15+ sequential DB queries per checkout
+// Hypothesis: N+1 query in payment method loading
+
+// 4. Add instrumentation
+span.setAttribute('debug.queryCount', queryCount);
+span.setAttribute('debug.paymentMethodId', methodId);
+
+// 5. Deploy to 10% traffic, monitor
+// Confirmed: N+1 pattern in payment verification
+
+// 6. AI generates fix
+// Replace sequential queries with batch query
+
+// 7. Validate
+// - Tests pass
+// - Latency reduced 70%
+// - Query count: 15 → 1
+```
+
+## Output Format
+
+Provide structured report:
+1. **Issue Summary**: Error, frequency, impact
+2. **Root Cause**: Detailed diagnosis with evidence
+3. **Fix Proposal**: Code changes, risk, impact
+4. **Validation Plan**: Steps to verify fix
+5. **Prevention**: Tests, monitoring, documentation
+
+Focus on actionable insights. Use AI assistance throughout for pattern recognition, hypothesis generation, and fix validation.
+
+---
+
+Issue to debug: $ARGUMENTS

package/merged-commands/error-handling-patterns.md

@@ -0,0 +1,35 @@
+---
+name: error-handling-patterns
+description: Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
+---
+
+# Error Handling Patterns
+
+Build resilient applications with robust error handling strategies that gracefully handle failures and provide excellent debugging experiences.
+
+## Use this skill when
+
+- Implementing error handling in new features
+- Designing error-resilient APIs
+- Debugging production issues
+- Improving application reliability
+- Creating better error messages for users and developers
+- Implementing retry and circuit breaker patterns
+- Handling async/concurrent errors
+- Building fault-tolerant distributed systems
+
+## Do not use this skill when
+
+- The task is unrelated to error handling patterns
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.