IssueVista/.coderabbit.yaml at master · VibeTensor/IssueVista · 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
# CodeRabbit AI Configuration for IssueVista
# https://docs.coderabbit.ai/guides/configure-coderabbit

language: en-US
early_access: false
reviews:
  profile: chill
  request_changes_workflow: false
  auto_approve:
    enabled: true
  high_level_summary: true
  poem: false
  review_status: true
  collapse_walkthrough: false
  auto_review:
    enabled: true
    drafts: false
  tools:
    github-checks:
      enabled: true
      timeout_ms: 90000
    eslint:
      enabled: false
    prettier:
      enabled: false
  path_filters:
    - '!**/*.lock'
    - '!**/*.svg'
    - '!**/dist/**'
    - '!**/node_modules/**'
    - '!**/.astro/**'
  path_instructions:
    - path: '**/*'
      instructions: |
        ## Project Context
        IssueVista is a web application built with Astro 5.x, Svelte 5, and UnoCSS that helps developers find unassigned GitHub issues without pull requests.

        ## Review Focus
        - TypeScript type safety
        - Svelte component best practices
        - Accessibility (a11y) compliance
        - Mobile responsiveness
        - Performance optimizations
        - Security considerations (especially for GitHub API usage)
        - Code clarity and maintainability

        ## Coding Standards
        - Use TypeScript for type safety
        - Follow functional programming principles where applicable
        - Keep components small and focused
        - Write self-documenting code with clear variable names
        - Add comments for complex logic only
        - Ensure mobile-first responsive design
        - Test all changes on both desktop and mobile

        ## What to Flag
        - Missing or incorrect TypeScript types
        - Accessibility issues (missing alt text, ARIA labels, etc.)
        - Performance issues (unnecessary re-renders, large bundles)
        - Security vulnerabilities (XSS, API key exposure)
        - Breaking changes without documentation
        - Code duplication
        - Missing error handling
        - Hard-coded values that should be configurable

chat:
  auto_reply: true

knowledge_base:
  learnings:
    scope: global
  opt_out: false