aiox-core/.coderabbit.yaml at main · SynkraAI/aiox-core · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
# AIOX CodeRabbit Configuration
# Story: COLLAB-1, 12.11
# Created: 2025-12-30
# Updated: 2026-02-05 (Story 12.11 - Bob CI/CD Pipeline)
#
# CodeRabbit provides AI-powered code review for pull requests
# Documentation: https://docs.coderabbit.ai/getting-started/yaml-configuration

language: "en-US"
tone_instructions: "Be professional, constructive, and focused on code quality."
early_access: false

reviews:
  # Automatic review settings
  auto_review:
    enabled: true
    base_branches:
      - main
    drafts: false

  # Review behavior
  request_changes_workflow: true
  high_level_summary: true
  poem: false
  review_status: true
  collapse_walkthrough: false

  # Path-specific review instructions (array format per schema)
  path_instructions:
    - path: ".aiox-core/core/**"
      instructions: |
        CRITICAL PATH: Core framework modules require thorough review.
        Verify error handling is comprehensive with proper try/catch and error context.
        Check for race conditions in orchestration modules (lock-manager, session-state).
        Validate async/await patterns and ensure no unhandled promise rejections.
        Ensure backwards compatibility — core modules are consumed by all agents.
        Check for proper input validation on public API methods.
        Verify test coverage exists for new/modified functions.
        Flag any hardcoded paths, credentials, or environment-specific values.

    - path: ".aiox-core/core/orchestration/**"
      instructions: |
        Bob orchestration modules — highest scrutiny required.
        Verify bob-orchestrator.js maintains single-responsibility for workflow dispatch.
        Check lock-manager.js for deadlock prevention and proper cleanup.
        Validate terminal-spawner.js handles all platforms (Unix shell, Windows fallback).
        Ensure workflow-executor.js callback lifecycle is correct (onStart, onComplete, onError).
        Check session-state.js for thread-safety and state corruption prevention.
        Verify message-formatter.js output is consistent across all message types.

    - path: ".aiox-core/development/agents/**"
      instructions: |
        Verify agent follows AIOX agent YAML structure (persona_profile, commands, dependencies).
        Check that persona_profile includes archetype, communication style, and greeting_levels.
        Validate all commands listed have corresponding task dependencies.
        Ensure agent has proper visibility metadata for commands.
        Check for security: no hardcoded credentials or sensitive data.

    - path: ".aiox-core/development/tasks/**"
      instructions: |
        Verify task follows AIOX task format with clear elicitation points.
        Check that deliverables are well-defined.
        Validate any referenced dependencies exist in the codebase.
        Ensure task has proper error handling guidance.

    - path: ".aiox-core/development/workflows/**"
      instructions: |
        Verify workflow YAML structure is valid.
        Check step ordering and dependencies make logical sense.
        Validate referenced agents and tasks exist.

    - path: ".aiox-core/product/templates/**"
      instructions: |
        Ensure template follows AIOX template conventions.
        Check placeholder syntax is consistent.
        Validate template produces valid output.

    - path: ".github/**"
      instructions: |
        Review for security implications.
        Check for proper secret handling.
        Validate workflow syntax.
        Ensure consistent with existing CI patterns.

    - path: "**/*.js"
      instructions: |
        Check for async/await best practices.
        Verify error handling is comprehensive.
        Look for potential security vulnerabilities.
        Ensure code follows AIOX coding standards (ES2022, single quotes, 2-space indent).

    - path: "**/*.ts"
      instructions: |
        Verify TypeScript types are properly defined.
        Check for any 'any' type usage that should be more specific.
        Ensure exports are properly typed.

# Chat settings
chat:
  auto_reply: true