.pr_agent.toml

[config]
add_repo_metadata = true

[github_app]
pr_commands = [
  "/agentic_describe",
  "/agentic_review"
]

[pr_code_suggestions]
extra_instructions = """\
- Check PR checks (actions, etc) before suggesting changes that you think will fix compilation errors. If the checks pass, it means that there are no compilation errors, and no suggestions are required (missing imports, using statements, etc).
- When suggesting to follow the framework patterns, like ASP.NET Core and Blazor, always make sure that the code you are going to suggest is indeed following the latest version of the framework.
"""

[pr_to_ticket]
default_project_key = "DB"
default_base_url = "https://linear.app/kurrent"
linear_base_url = "https://linear.app/kurrent" 
fallback_to_git_provider_issues = false

[pr_compliance]
extra_instructions = """\
- Do not apply audit logging compliance requirements to tests
- For robust error handling and edge cases compliance, when suggesting checks for null values, make sure that the contract allows nulls. If fields or properties in question aren't nullable, do not apply null check suggestions.
- Only apply comprehensive audit log rules for clear cases where issuing an error or a warning makes sense. Otherwise, there's no requirement for audit logs.
- Before suggesting audit compliance improvements, make sure the relevant context is available. For example, a function that has no user context cannot produce audit log with user details.
- Audit log compliance improvements should only be suggested when handling user-initiated administrative operations.
- When in doubt about null checks, make sure that the property or field is indeed nullable. Rely on compiler warnings in build results for questionable null check practices.
"""

[pr_reviewer]
check_pr_additional_content=true

[rag_arguments]
enable_rag=true

[pr_description]
auto_create_ticket = true