language: en-US tone_instructions: '' early_access: false enable_free_tier: true reviews: slop_detection: enabled: true label: 'slop' profile: assertive request_changes_workflow: false high_level_summary: true high_level_summary_instructions: | Start the summary with an "ELI5" (Explain Like I'm 5) section at the very top that gives a simple, jargon-free explanation of what the PR does and why, in 1-3 sentences that anyone could understand. high_level_summary_placeholder: '@coderabbitai summary' high_level_summary_in_walkthrough: false auto_title_placeholder: '@coderabbitai' auto_title_instructions: '' review_status: true commit_status: true fail_commit_status: false collapse_walkthrough: false changed_files_summary: true sequence_diagrams: false estimate_code_review_effort: true assess_linked_issues: true related_issues: true related_prs: true suggested_labels: true labeling_instructions: [] auto_apply_labels: false suggested_reviewers: true auto_assign_reviewers: false in_progress_fortune: true poem: false path_filters: [] path_instructions: - path: '.changeset/*.md' instructions: | Changeset files are really important for keeping track of changes in the project. They'll be used to generate release notes and inform users about updates. Review the changeset file according to these guidelines: - The target audience are developers - Write short, direct sentences that anyone can understand. Avoid technical jargon, and acronyms. Use action-oriented verbs (Added, Fixed, Improved, Deprecated, Removed) - Commit messages (e.g. "fix: correct minor typos") are not allowed as descriptions in changeset files. - Avoid generic phrases like "Update code", "Miscellaneous improvements", or "Bug fixes" - Highlight outcomes! What does change for the end user? Do not focus on internal implementation details - If the change is a breaking change or is adding a new feature, ensure that a short code example is provided. This code example should show the public API usage. Do not show code examples of internal implementation details. - For breaking changes, include short, concise before/after instructions (and use migration guides in the docs for the complete instructions) - Keep the formatting easy-to-read and scannable. If necessary, use bullet points or multiple paragraphs (Use **bold** text as the heading for these sections, do not use markdown headings). - Each changeset file contains a YAML frontmatter at the top. It will be one or more package names followed by a colon and the type of change (patch, minor, major). Do not modify this frontmatter. Check that the description inside the changeset file only applies to the packages listed in the frontmatter. Do not allow descriptions that mention changes to packages not listed in the frontmatter. In these cases, the user must create a separate changeset file for those packages. - Very long changesets in one file (with multiple packages in the frontmatter) are an anti-pattern. This will lead to multiple packages having really large changelog entries. This must be avoided. - If the changes span multiple packages and each change is different from another, you MUST create multiple changeset files. Otherwise you'll mix different changes into changeset files where they don't belong. For this you must decide what logical groups exist. In case of a guideline violation ALWAYS mark your comment as `potential_issue`. - path: '**/*.{ts,tsx}' instructions: | For schema-backed executions, deterministic input and output contract validation belongs in `inputSchema`, `outputSchema`, or their schema fields—not inline in `execute`. Flag duplicated inline checks for payload shape, types, enum membership, ranges, formats, and cross-field invariants. Each finding must identify the inline validation and the schema where it belongs. Do not report checks that require runtime context or mutable/external state, including authorization, database or filesystem state, resource existence, conflicts, request context, or external-service responses; those belong in `execute`. - path: 'packages/connect/src/providers/**' instructions: | Any new provider added under `packages/connect/src/providers//` must ship with a smoke-test scenario at `packages/connect/scripts/smoke-test/scenarios/.ts`, registered alphabetically in `scenarios/index.ts`, covering 100% of the provider's tools (verifiable via `tsx packages/connect/scripts/smoke-test/audit-coverage.ts`). When a PR adds or regenerates a provider under this path, check for: - Scenario file exists at `packages/connect/scripts/smoke-test/scenarios/.ts` and is registered alphabetically in `scenarios/index.ts`. - Every tool shipped by the provider appears in the scenario's step list, invoked through the public tools resolver (not direct SDK calls). - Self-contained create/read/update/delete lifecycle — the scenario creates its own prerequisite resources tagged with the `runId` helper and deletes everything it creates. - Cleanup steps are wrapped in `try/catch`. On cleanup failure the scenario calls `log.error(...)` naming the leaked record and records the step as `fail` (not `skip`). - `probeTool()` from `scenario.ts` is used only for operations that genuinely cannot bootstrap prerequisites (synthetic ids, product-tier-gated endpoints, operations that touch real recipients or billable resources) and carries an inline comment explaining why. - PR description includes the live pass count from `pnpm --filter @mastra/connect smoke-test --provider `. See `packages/connect/AGENTS.md` and `packages/connect/scripts/smoke-test/README.md` for the full policy. In case of a guideline violation ALWAYS mark your comment as `potential_issue`. abort_on_close: true disable_cache: false auto_review: enabled: true auto_incremental_review: true ignore_title_keywords: [] labels: [] drafts: false base_branches: [] ignore_usernames: - daneatmastra - 'dane-ai-mastra[bot]' finishing_touches: docstrings: enabled: true unit_tests: enabled: true pre_merge_checks: docstrings: mode: warning threshold: 80 title: mode: warning requirements: 'Title should be concise and descriptive, ideally under 50 characters. Avoid generic phrases like "Update code" or "Fix bug". Use imperative mood and proper capitalization.' description: mode: warning issue_assessment: mode: warning custom_checks: [] tools: ast-grep: rule_dirs: [] util_dirs: [] essential_rules: true packages: [] shellcheck: enabled: true markdownlint: enabled: true github-checks: enabled: true timeout_ms: 90000 languagetool: enabled: true enabled_rules: [] disabled_rules: [] enabled_categories: [] disabled_categories: [] enabled_only: false level: default biome: enabled: true hadolint: enabled: true yamllint: enabled: true gitleaks: enabled: true checkov: enabled: true eslint: enabled: false actionlint: enabled: true semgrep: enabled: true sqlfluff: enabled: true prismaLint: enabled: true oxc: enabled: true dotenvLint: enabled: true htmlhint: enabled: true checkmake: enabled: true osvScanner: enabled: true chat: art: true auto_reply: true integrations: linear: usage: auto knowledge_base: opt_out: false web_search: enabled: true code_guidelines: enabled: true filePatterns: - '**/AGENTS.md' - '**/CLAUDE.md' learnings: scope: auto issues: scope: auto linear: usage: auto team_keys: [] pull_requests: scope: auto mcp: usage: auto disabled_servers: [] code_generation: docstrings: language: en-US path_instructions: [] unit_tests: path_instructions: [] issue_enrichment: planning: enabled: true