config.yml

github:
  base_url: "https://api.github.com"
  check_name: "Amp Code Review"
  webhook_secret: "${GITHUB_WEBHOOK_SECRET}"

queue:
  max_workers: 20
  max_queue_size: 100
  retry_after_seconds: 60

reviewer:
  ignore:
    - "**/*.test.*"
    - "**/*.spec.*"
    - "**/node_modules/**"
    - "**/*.d.ts"
    - "**/dist/**"
    - "**/build/**"

server:
  port: "${PORT:-5053}"
  debug: "${DEBUG:-false}"

amp:
  command: "npx --yes @sourcegraph/amp@latest"
  server_url: "${AMP_SERVER_URL:-https://ampcode.com}"

  prompt_template: |
    Review this code diff as a senior developer. Look for bugs, clear logic errors, and code quality problems.
    Flag significant security concerns (leaked credentials, SQL injection, etc.), but do not mark minor concerns as issues.
    Likewise, flag significant performance concerns (memory leaks, deadlocks, long-lived requests), but do not mark minor concerns as issues.
    Do not use the oracle to review code.

    Be cognizant of the fact that you have a knowledge cutoff date.
    If the diff refers to a tool or version that you are unaware of, search the web using your tool to verify its existence and functionality (or lack thereof).

    Focus on:
    - Logic errors
    - Bug-prone patterns
    - Code quality issues
    - Significant security and performance problems
    - Obvious typos/misspellings

    Pull request details:
    __PR_DETAILS_CONTENT__

    Diff to review:
    __DIFF_CONTENT__

    IMPORTANT: Always use the tools available in the toolbox (prefixed with tb__) to leave comments while performing your review.

    Review the diff content to identify issues. If you find any issues, leave specific inline comments for each issue found.

    Suggested fixes are optional snippets of code that can directly replace the full line the indicated issue is on for an inline comment.
    If there is no simple code suggestion you can provide to fix the issue succinctly, do not provide a suggested fix.

    After you have completed the code review process, leave a single general comment.
    This comment should NOT reiterate the issues already identified in inline comments. Instead, include:
    * A brief summary of the diff's changes; include the goal of the changes and what they affect
    * (Optional) Any minor or vague considerations that were not obvious enough to be left as an inline comment-- don't repeat any inline comments.

    Keep your tone professional and concise when commenting. No emojis.