Custom Context

For each repository, Tenki Reviewer can use a configuration file to define custom rules and specific settings.

This file provides persistent guidance that Tenki Code Reviewer applies to every review in that repository.

Manually create the .md file and save it in your codebase. Then, add its path to the Custom Context Panel so it can be applied to the selected repository.

The Custom Context file is intentionally flexible. You can include any instructions you want the agent to consistently apply, for example:

• Team rules you always want reviewed: Coding standards, security requirements, architectural constraints, or internal best practices.
• Areas to focus on: Critical paths, high-risk modules, legacy code, or performance-sensitive components.
• Things to ignore: Generated files, vendor code, migrations, or any changes you don’t want reviewed.
• Project-specific guidance: Domain assumptions, business rules, or constraints that are unique to your product.