chore(ci): attempting to make Bito smarter

[Charles Hudson (phobetron)]

Adds TypeScript-specific review guidance requiring Bito to verify repository usage, public entry points, generic defaults, overloads, narrowing, and test intent before raising findings. This is intended to reduce the false positives encountered during a previous PR and affects review configuration only—no runtime or type API changes.

[NT-3770]

[bito-code-review]

Code Review Agent Run #3ff8df

Actionable Suggestions - 0

Review Details

• Files reviewed - 2 · Commit Range: 9824566..9824566

  • .bito.yaml
  • .bito/guidelines/typescript-review-evidence.txt
• Files skipped - 0
• Tools

  • Whispers (Secret Scanner) - ✔︎ Successful
  • Detect-secrets (Secret Scanner) - ✔︎ Successful

---

Bito Usage Guide

Commands

Type the following command in the pull request comment and save the comment.

• /review - Manually triggers a full AI review.

• /pause - Pauses automatic reviews on this pull request.

• /resume - Resumes automatic reviews.

• /resolve - Marks all Bito-posted review comments as resolved.

• /abort - Cancels all in-progress reviews.

Refer to the documentation for additional commands.

Configuration

This repository uses Default Agent You can customize the agent settings here or contact your Bito workspace admin at jared.jolton@contentful.com.

Documentation & Help

• Customize agent settings
• Review rules
• General documentation
• FAQ

AI Code Review powered by

[bito-code-review]

Functional Validation by Bito

Source	Requirement / Code Area	Status	Notes
NT-3770	Bito must not inject AI-generated content into PR descriptions	✅ Met	Bito configuration in .bito.yaml has `post_description: false` and `post_changelist: false` (lines 2-3), which disables AI-generated content injection into PR descriptions as required.
NT-3770	Review comments must contain only actionable findings from the Actionable Suggestions tier	✅ Met	Review comments are configured to contain only actionable findings: `suggestion_mode: essential` (line 1) limits comments to high-signal findings, and `linters_feedback: false` (line 6) suppresses duplicate mechanical feedback already caught by ESLint/TypeScript/Prettier. The new .bito/guidelines/typescript-review-evidence.txt provides evidence-based rules ensuring findings survive scrutiny before posting.
NT-3770	Boilerplate content must be removed from review comments	✅ Met	The `suggestion_mode: essential` setting in .bito.yaml (line 1) suppresses boilerplate sections (Bito Usage Guide, Review Details) from review comments, reducing noise as required.
NT-3770	Routine mechanical PRs must produce no review comments	✅ Met	The `suggestion_mode: essential` setting in .bito.yaml (line 1) ensures Bito only posts comments when genuine actionable findings exist. Routine mechanical PRs with no real findings will produce no comments, as the essential mode only triggers on meaningful issues.

[bito-code-review]

Impact Analysis by Bito

Code Paths Analyzed

Impact:
No functional code changes. This PR adds TypeScript-specific review guidelines to the Bito configuration, extending the existing custom_guidelines framework with per_language rules.

Flow:
Configuration-only change: .bito.yaml updated to reference new typescript-review-evidence.txt guideline file.

Direct Changes (Diff Files):
• .bito.yaml [18-21] — Added per_language.typescript section referencing new guideline file
• .bito/guidelines/typescript-review-evidence.txt [1-43] — New file containing TypeScript-specific code review rules covering unused declarations, public exports, generics/overloads, type narrowing, test intent, and pipeline ownership

Repository Impact:
• Bito AI code review configuration: TypeScript files in this repo will now be reviewed against these evidence-based guidelines

Cross-Repository Dependencies:
• None.

Database/Caching Impact:
• None

API Contract Violations:
• None.

Infrastructure Dependencies:
• None.

Additional Insights:
• Code review quality for TypeScript: New guidelines emphasize evidence-based findings: checking whole files before marking declarations unused, verifying package entrypoints before suggesting exports, distinguishing public overloads from implementation signatures

Testing Recommendations

Frontend Impact:
• None.

Service Integration:
• None.

Data Serialization:
• None.

Privacy Compliance:
• None.

Backward Compatibility:
• None.

OAuth Functionality:
• None

Reliability Testing:
• None

Additional Insights:
• Verify the new guideline file is valid YAML and accessible at the configured path
• Confirm Bito AI successfully loads and applies the per_language.typescript configuration
• Test that TypeScript files in the repo are reviewed using the new guidelines

_{Analysis based on known dependency patterns and edges. Actual impact may vary.}

[bito-code-review]

✅ Review Settings Overridden

Status: Overridden Successfully

Guidelines:

• Accepted:

  • General : Review Posture, Repo Truth And Boundaries, Domain Invariants

  • Language : typescript = TypeScript Review Evidence

Note: Extra guidelines beyond 3 general purpose guidelines and 1 language specific guideline per language are not processed. Guidelines are fetched from the source branch.