qa-service

name	qa-service
description	Continuous Quality Assurance service agent that monitors development activities in real-time, automatically triggering quality analysis on code changes. Provides background processing for comprehensive QA validation across parallel development environments, ensuring consistent quality standards throughout the development lifecycle.
short_description	Continuous Quality Assurance service agent that monitors development activities in real-time, automatically triggering quality analysis on c

QA Service Agent Skill

Cursor Integration: This skill is auto-discovered by Cursor. It activates based on the task description matching the skill's capabilities.

Overview

Continuous Quality Assurance service agent that monitors development activities in real-time, automatically triggering quality analysis on code changes. Provides background processing for comprehensive QA validation across parallel development environments, ensuring consistent quality standards throughout the development lifecycle.

Capabilities

• Real-time Monitoring: File system change detection with intelligent debouncing
• Automatic QA Execution: Background quality analysis triggered by code modifications
• Multi-worktree Support: Parallel QA processing across isolated development environments
• Incremental Analysis: Smart analysis focusing on changed components only
• Quality Trend Tracking: Historical QA metrics and trend analysis
• Integration Status Monitoring: Continuous validation of merge readiness

Cursor Tools

This skill uses the following Cursor-native tools:

Tool	Purpose
Read	Read files from the codebase
Grep	Search for patterns in code (regex)
SemanticSearch	Find code by meaning, not exact text
Write	Create new files
StrReplace	Edit existing files with precise replacements
Shell	Execute terminal commands
WebSearch	Search the web for documentation/references
WebFetch	Fetch content from URLs
Task	Launch subagents for complex parallel work
ReadLints	Check for linter errors after edits

Usage Examples

Start Background QA Monitoring

Monitor Parallel Development

Quality Trend Analysis

Service Management

Output Format

QA Service Status Report

🔬 QA Service Status Report - Continuous Quality Assurance
══════════════════════════════════════════════════════════════════════════════╁E
Service Status: Active (Running)
Uptime: 2h 34m 12s
Monitoring: 4 worktrees
Last Activity: 2026-01-04 15:47:23 UTC

📊 Service Statistics
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━E
Total QA Runs: 127
Successful QA Runs: 118 (92.9% success rate)
Failed QA Runs: 9 (7.1% failure rate)
Files Processed: 2,847
Change Events Detected: 456
Average QA Duration: 34.2 seconds

🎯 Active Monitoring
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━E
Worktrees Being Monitored:
├── auth-feature (3 changes pending)
━E  ├── Last QA: ✁EPASSED (2 min ago)
━E  ├── Quality Score: A- (Good)
━E  └── Next Scheduled: Auto (on changes)
├── payment-feature (1 change pending)
━E  ├── Last QA: 🔄 RUNNING (45s elapsed)
━E  ├── Quality Score: B+ (Good)
━E  └── Next Scheduled: Auto (on changes)
├── ui-feature (12 changes pending)
━E  ├── Last QA: ❁EFAILED (5 min ago)
━E  ├── Quality Score: C (Needs Attention)
━E  └── Next Scheduled: Manual review required
└── api-feature (0 changes pending)
    ├── Last QA: ✁EPASSED (12 min ago)
    ├── Quality Score: A (Excellent)
    └── Next Scheduled: Auto (on changes)

⚙︁EService Configuration
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━E
Monitoring Paths: ./worktrees/
QA Interval: 300 seconds (5 minutes)
File Change Debounce: 2.0 seconds
Max Concurrent QA: 2
Auto-restart on Failure: Enabled
Log Retention: 7 days

📈 Quality Trends (Last 24 hours)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━E
┌─────────────────────┬─────────┬─────────┬─────────────┬─────────────━E
━ETime Period         ━EQA Runs ━ESuccess ━EAvg Score   ━EIssues Found━E
├─────────────────────┼─────────┼─────────┼─────────────┼─────────────┤
━E00:00 - 06:00       ━E12      ━E100%    ━EA-          ━E3           ━E
━E06:00 - 12:00       ━E28      ━E93%     ━EB+          ━E12          ━E
━E12:00 - 18:00       ━E45      ━E91%     ━EB           ━E18          ━E
━E18:00 - 24:00       ━E42      ━E88%     ━EB-          ━E25          ━E
└─────────────────────┴─────────┴─────────┴─────────────┴─────────────━E

🚨 Active Alerts
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━E
1. ⚠EEui-feature: Multiple QA failures detected
   - Last 3 QA runs failed
   - Issues: Security vulnerabilities, performance bottlenecks
   - Recommendation: Code review and fixes required

2. 📉 Quality Trend: Declining code quality scores
   - Average score dropped from A- to B- in 6 hours
   - Primary issues: Algorithmic complexity, error handling
   - Recommendation: Team training on best practices

🔄 Current QA Executions
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━E
1. payment-feature (PID: 18473)
   - Progress: 68% complete
   - ETA: 23 seconds
   - Current Phase: Security Analysis

2. background-audit (PID: 18492)
   - Progress: 34% complete
   - ETA: 4 minutes 12 seconds
   - Current Phase: Performance Benchmarking

💡 Service Recommendations
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━E
1. Address ui-feature QA failures immediately
2. Schedule team training on security best practices
3. Consider increasing QA frequency for high-activity worktrees
4. Review and optimize QA analysis performance

📁 Service Artifacts
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━E
├── qa-service-logs/
━E  ├── qa-service.log (2.3MB)
━E  ├── error.log (145KB)
━E  └── audit.log (892KB)
├── qa-metrics/
━E  ├── quality-trends.json
━E  ├── performance-metrics.json
━E  └── worktree-stats.json
└── qa-reports/
    ├── latest-qa-summary.md
    ├── quality-dashboard.html
    └── alert-history.json

⚡ Performance Metrics
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━E
CPU Usage: 12.3% average
Memory Usage: 245MB peak
Disk I/O: 1.2GB transferred
Network: 0MB (local monitoring only)
Uptime: 99.7% availability

🎯 Next Maintenance Window
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━E
Scheduled: 2026-01-05 02:00 UTC
Tasks: Log rotation, metric aggregation, service restart
Estimated Duration: 15 minutes

QA Execution Details

{
  "qa_service_execution": {
    "execution_id": "qa-exec-2026-01-04-154723",
    "worktree": "payment-feature",
    "trigger": "file_change",
    "start_time": "2026-01-04T15:47:23Z",
    "estimated_completion": "2026-01-04T15:48:15Z",
    "progress_percentage": 68,
    "current_phase": "security_analysis",
    "phases_completed": [
      "file_analysis",
      "syntax_validation",
      "dependency_check"
    ],
    "phases_remaining": [
      "security_analysis",
      "performance_analysis",
      "code_quality_analysis",
      "integration_testing"
    ],
    "resource_usage": {
      "cpu_percent": 45.2,
      "memory_mb": 156,
      "disk_io_kb": 2340
    },
    "change_summary": {
      "files_changed": 3,
      "lines_added": 127,
      "lines_deleted": 23,
      "critical_files_modified": ["src/auth/mod.rs", "src/payment/handler.rs"]
    }
  }
}

Service Architecture

Monitoring Engine

• File System Watcher: Real-time change detection with platform-specific implementations
• Event Debouncing: Intelligent filtering to prevent excessive QA triggers
• Queue Management: Prioritized processing of QA requests
• Resource Limiting: Controlled concurrent QA execution

QA Orchestration

• Worktree Isolation: Independent QA analysis per development environment
• Incremental Analysis: Smart analysis focusing on changes and dependencies
• Result Caching: Performance optimization through intelligent caching
• Failure Recovery: Robust error handling and retry mechanisms

Reporting System

• Real-time Status: Live monitoring dashboards and status updates
• Historical Trends: Long-term quality metrics and trend analysis
• Alert System: Configurable notifications for quality issues
• Integration Reports: CI/CD and development tool integration

Configuration

Service Configuration

{
  "qa_service": {
    "monitoring_paths": ["./worktrees/", "./src/"],
    "qa_interval_seconds": 300,
    "file_change_debounce_seconds": 2.0,
    "max_concurrent_qa_runs": 2,
    "auto_restart_on_failure": true,
    "log_retention_days": 7,
    "enable_performance_monitoring": true
  }
}

Worktree Integration

{
  "worktree_integration": {
    "auto_discover_worktrees": true,
    "worktree_base_path": "./worktrees/",
    "qa_on_worktree_creation": true,
    "qa_on_file_changes": true,
    "qa_on_schedule": true,
    "merge_blocking_qa": true
  }
}

Alert Configuration

{
  "alerts": {
    "qa_failure_threshold": 3,
    "quality_score_decline_threshold": 1.0,
    "alert_channels": ["slack", "discord", "email"],
    "alert_cooldown_minutes": 30,
    "escalation_rules": {
      "critical_issues": "immediate",
      "quality_regression": "team_lead",
      "performance_degradation": "devops_team"
    }
  }
}

Quality Gates

{
  "quality_gates": {
    "block_on_critical_issues": true,
    "block_on_high_issues": false,
    "require_minimum_score": "B-",
    "max_qa_duration_seconds": 600,
    "require_clean_build": true,
    "require_test_coverage": 0.8
  }
}

Integration Points

Development Workflow Integration

# Start QA monitoring for current session
the qa-service skill "Start monitoring development session"

# Get real-time QA status
the qa-service skill "Show current QA status and active analyses"

# Pause/resume monitoring
the qa-service skill "Pause QA monitoring during refactoring"
the qa-service skill "Resume QA monitoring"

Worktree Manager Integration

# QA service automatically monitors new worktrees
the worktree-manager skill "Create feature worktree"
# ↁEQA service automatically starts monitoring

# Manual QA trigger
the qa-service skill "Run QA analysis on auth-feature worktree"

CI/CD Pipeline Integration

# GitHub Actions integration
- name: QA Service Status Check
  run: |
    the qa-service skill "Check service health and report status"

- name: Generate QA Trend Report
  run: |
    the qa-service skill "Generate quality trend report for CI"

IDE Integration

// VS Code extension configuration
{
  "codex.qaService": {
    "enableRealTimeMonitoring": true,
    "showQualityIndicators": true,
    "alertOnQAFailures": true,
    "autoFixSuggestions": true
  }
}

Performance Optimization

Resource Management

• CPU Limiting: Configurable CPU usage limits per QA run
• Memory Management: Automatic cleanup and memory monitoring
• Disk I/O Optimization: Efficient file access patterns
• Concurrent Limiting: Controlled parallelism to prevent resource exhaustion

Analysis Optimization

• Incremental Processing: Only analyze changed files and dependencies
• Caching Strategies: Intelligent caching of analysis results
• Parallel Analysis: Concurrent processing of independent components
• Early Termination: Stop analysis on critical failures

Monitoring Optimization

• Event Filtering: Smart filtering of irrelevant file changes
• Batch Processing: Group related changes for efficient processing
• Priority Queuing: High-priority changes processed first
• Load Balancing: Distribute QA load across available resources

Troubleshooting

Service Startup Issues

# Check service status
the qa-service skill "Check service status"

# Restart service
the qa-service skill "Restart QA service"

# Check logs
tail -f qa-service-logs/qa-service.log

File Monitoring Problems

# Verify file system permissions
ls -la ./worktrees/

# Test file change detection
echo "test" > ./worktrees/test-worktree/test.txt
the qa-service skill "Check for pending changes"

QA Execution Failures

# Check QA process status
ps aux | grep qa-service

# View detailed error logs
cat qa-service-logs/error.log | tail -50

# Run diagnostic QA
the qa-service skill "Run diagnostic QA analysis"

Performance Issues

# Monitor resource usage
the qa-service skill "Show performance metrics"

# Adjust configuration
the qa-service skill "Update config max_concurrent_qa_runs=1"

# Clear caches
the qa-service skill "Clear analysis caches"

Best Practices

Service Management

1. Regular Monitoring: Daily status checks and performance monitoring
2. Log Rotation: Automatic cleanup of old log files
3. Backup Configuration: Regular backup of service configuration
4. Version Updates: Keep QA rules and analysis engines updated

Quality Assurance

1. Baseline Establishment: Establish quality baselines for each worktree
2. Trend Monitoring: Regular review of quality trends and metrics
3. Alert Tuning: Fine-tune alert thresholds based on team tolerance
4. Feedback Integration: Use QA results to improve development practices

Resource Optimization

1. Load Balancing: Distribute QA load across development phases
2. Off-hours Processing: Schedule intensive analysis during low-activity periods
3. Caching Strategies: Maximize cache hit rates for repeated analyses
4. Resource Limits: Set appropriate limits to prevent system impact

Team Integration

1. Training Programs: Educate team on QA feedback interpretation
2. Process Integration: Make QA checks part of standard development workflow
3. Communication: Clear communication of QA requirements and expectations
4. Continuous Improvement: Regular review and improvement of QA processes

• Continuous Integration Best Practices
• Quality Assurance in Software Development
• Real-time Monitoring Patterns

---

$ the skill-install skill https://github.com/zapabob/codex-qa-service-skill` Version: 2.10.0