3

overriding rules

Alexey Efimchik edited this page 2026-03-25 12:02:46 +07:00

Table of Contents

• ⚙️ Overriding Review Rules
• 📌 Introduction
• 🔀 Override Methods - Select one of the options from the list below
• 📁 Method 1: Overriding via a folder
• 1.1. Example content for PROMPT.md, ALLOWED_TOOLS.md and DISALLOWED_TOOLS.md files
• 📋 Method 2: Overriding via script arguments
• 2.1. Example content for cc_prompt, cc_allowed_tool and cc_disallowed_tool action parameters
• ⚠️ Important Limitations
• ✅ Value for the cc_allowed_tool parameter and the ALLOWED_TOOLS.md file
• ✅ Value for the cc_disallowed_tool parameter and the DISALLOWED_TOOLS.md file

⚙️ Overriding Review Rules

📌 Introduction

This section describes the basic principles of redefining the built-in prompt of the tool. This can be used to create your own rules during review.

Be careful — when you override the rules, you override the entire prompt, including all review logic, output format, and tool permissions. ⚠️ Important! When you override settings, you must override all settings at once: the prompt, allowed tools, and disallowed tools. You do this by specifying the options_type parameter in the Gitea action.

🔀 Override Methods - Select one of the options from the list below

📁 Method 1: Overriding via a folder

Set the options_type parameter to "folder" and create a .review/ folder in your repository with these 3 files:

my-project/
├── .review/
│   ├── PROMPT.md
│   ├── ALLOWED_TOOLS.md
│   └── DISALLOWED_TOOLS.md
├── src/
└── ...

Gitea action example:

name: AI Code Reviewer Assistant for Gitea
on:
  issue_comment:
    types: [created]
  pull_request_review_comment:
    types: [created]
  pull_request:
    types: [opened, synchronize, reopened]
jobs:
  claude-assistant:
    runs-on: kodo-review
    steps:
      - name: Run AI Code Reviewer
        uses: https://code.wynenterprise.io/kodo/reviewer@main
        with:
          gitea_token: ${{ secrets.CC_GITEATOKEN }}
          anthropic_api_key: ${{ secrets.CC_API_KEY }}
          options_type: "folder"

1.1. Example content for PROMPT.md, ALLOWED_TOOLS.md and DISALLOWED_TOOLS.md files

Take a look at this example of custom settings for a specific domain; use it as an exemple for creating your own settings:

• 📝 Technical Writing & Documentation Review — grammar, clarity, structure, and content quality for docs and articles
• 🔒 Security Review — vulnerabilities, unsafe patterns, OWASP Top 10, secrets exposure
• ⚡ Performance Review — bottlenecks, N+1 queries, memory leaks, algorithmic complexity

Each template page contains a ready-to-use prompt, allowed tools list, and disallowed tools list, along with usage examples for both override methods.

📋 Method 2: Overriding via script arguments

Set the options_type parameter to "arguments" and pass the following three parameters directly in the action:

Parameter	Description	Required
cc_prompt	New prompt for review	Yes
cc_allowed_tool	List of allowed tools for the AI agent	Yes
cc_disallowed_tool	List of disallowed tools for the AI agent	Yes

Gitea action example:

name: AI Code Reviewer Assistant for Gitea
on:
  issue_comment:
    types: [created]
  pull_request_review_comment:
    types: [created]
  pull_request:
    types: [opened, synchronize, reopened]
jobs:
  claude-assistant:
    runs-on: kodo-review
    steps:
      - name: Run AI Code Reviewer
        uses: https://code.wynenterprise.io/kodo/reviewer@main
        with:
          gitea_token: ${{ secrets.CC_GITEATOKEN }}
          anthropic_api_key: ${{ secrets.CC_API_KEY }}
          cc_prompt: "New review rules for AI agent"
          cc_allowed_tool: "List of allowed tools for AI agent"
          cc_disallowed_tool: "List of disallowed tools for AI agent"
          options_type: "arguments"

Replace the values of cc_prompt, cc_allowed_tool, and cc_disallowed_tool with your actual content.

2.1. Example content for cc_prompt, cc_allowed_tool and cc_disallowed_tool action parameters

Take a look at this example of custom settings for a specific domain; use it as an exemple for creating your own settings:

• 📝 Technical Writing & Documentation Review — grammar, clarity, structure, and content quality for docs and articles
• 🔒 Security Review — vulnerabilities, unsafe patterns, OWASP Top 10, secrets exposure
• ⚡ Performance Review — bottlenecks, N+1 queries, memory leaks, algorithmic complexity

Each template page contains a ready-to-use prompt, allowed tools list, and disallowed tools list, along with usage examples for both override methods.

⚠️ Important Limitations

✅ Value for the cc_allowed_tool parameter and the ALLOWED_TOOLS.md file

The list of allowed tools must always include the following:

Bash, Edit, MultiEdit, Glob, Grep, LS, Read, Write, mcp__serena, mcp__gitea__get_pull_request_by_index, mcp__gitea__list_repo_pull_requests, mcp__gitea__list_repo_commits, mcp__gitea__create_pull_request_review, mcp__gitea__get_pull_request_review, mcp__gitea__list_pull_request_reviews, mcp__gitea__delete_pull_request_review, mcp__gitea__dismiss_pull_request_review, mcp__gitea__submit_pull_request_review, mcp__gitea__get_issue_by_index, mcp__gitea__list_pull_request_review_comments, mcp__gitea__get_file_content, mcp__gitea__create_issue, mcp__gitea__get_dir_content, mcp__gitea__edit_issue, mcp__gitea__get_issue_comments_by_index, mcp__gitea__create_issue_comment

You can expand it by adding your own, but we do not recommend removing anything from it.

✅ Value for the cc_disallowed_tool parameter and the DISALLOWED_TOOLS.md file

The list of disallowed tools must always include the following:

WebSearch, Bash(git diff:*), Bash(git push:*), Bash(rm:*), Bash(git diff:*)

You can expand it by adding your own, but we do not recommend removing anything from it.

🤖 Kodo AI Reviewer

• What is Kodo?

---

📚 Gitea

👩‍💻 Developer

• Code Review with Kodo
• Review Output Format
• Limitations & Best Practices

🧑‍🔧 Tech Lead

• CI/CD Integration
• Extension of Existing Review Rules
• Overriding Review Rules
  • Placeholder System
  • Template: Tech Writing
  • Template: Security
  • Template: Performance
• Troubleshooting
• Configuration and Parameters

---

📚 Bitbucket

👩‍💻 Developer

• Code Review with Kodo
• Review Output Format
• Limitations & Best Practices

🧑‍🔧 Tech Lead

• CI/CD Integration
• Extension of Existing Review Rules
• Overriding Review Rules
  • Placeholder System
  • Template: Tech Writing
  • Template: Security
  • Template: Performance
• Troubleshooting
• Configuration and Parameters

---

📚 Local Kodo

• Local Kodo Tool
  • Overriding Local Settings