detective-benno 0.1.0

An intelligent code review detective powered by LLM - solving code mysteries, one PR at a time

🔍 Detective Benno

"Every line of code tells a story. I find the plot holes." - Detective Benno

An intelligent code review detective powered by LLM that investigates your pull requests and uncovers bugs, security vulnerabilities, and code smells before they become problems.

Features

• Automated PR Investigation - Automatically triggered on pull request events
• Multi-language Support - Investigates Python, Go, JavaScript, TypeScript, Rust, and more
• Configurable Rules - Define custom investigation guidelines per repository
• GitHub Action - Easy integration with existing CI/CD pipelines
• CLI Tool - Investigate local changes before committing
• Diff-aware Analysis - Only investigates changed code, not entire files

Quick Start

Installation

pip install detective-benno

CLI Usage

# Investigate staged changes
benno investigate --staged

# Investigate specific files
benno investigate src/main.py src/utils.py

# Investigate a git diff
git diff main..feature | benno investigate --diff

# Investigate with custom guidelines
benno investigate --config .benno.yaml

GitHub Action

Add to your .github/workflows/detective-benno.yml:

name: Detective Benno Investigation

on:
  pull_request:
    types: [opened, synchronize]

jobs:
  investigate:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write

    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Detective Benno Investigation
        uses: bimakw/detective-benno@v1
        with:
          openai_api_key: ${{ secrets.OPENAI_API_KEY }}
          github_token: ${{ secrets.GITHUB_TOKEN }}
          investigation_level: detailed  # minimal, standard, detailed

Configuration

Create .benno.yaml in your repository root:

# Detective Benno Configuration
version: "1"

# Investigation settings
investigation:
  level: detailed          # minimal, standard, detailed
  max_findings: 10         # Maximum findings per investigation
  languages:               # Language-specific settings
    python:
      style_guide: pep8
      check_types: true
    go:
      style_guide: effective-go
    javascript:
      style_guide: airbnb

# Custom investigation guidelines
guidelines:
  - "Look for potential SQL injection vulnerabilities"
  - "Check for hardcoded credentials or secrets"
  - "Verify error handling is comprehensive"
  - "Ensure all functions have proper documentation"

# Ignore patterns
ignore:
  files:
    - "*.md"
    - "*.txt"
    - "vendor/**"
    - "node_modules/**"
  patterns:
    - "TODO:"  # Don't flag TODOs

# Model settings
model:
  provider: openai
  name: gpt-4o
  temperature: 0.3

Investigation Categories

Detective Benno investigates for:

Category	Description
Security	SQL injection, XSS, hardcoded secrets, unsafe operations
Performance	N+1 queries, unnecessary loops, memory leaks
Best Practices	Code style, naming conventions, design patterns
Error Handling	Missing try-catch, unhandled promises, panic recovery
Maintainability	Code duplication, complexity, documentation

Example Investigation Report

============================================
   DETECTIVE BENNO - INVESTIGATION REPORT
============================================

Case #: PR-142
Files Investigated: 3
Findings: 5 (2 critical, 2 warnings, 1 suggestion)

CRITICAL FINDINGS
-----------------

Location: src/auth.py:45
Evidence:
   query = f"SELECT * FROM users WHERE id = {user_id}"

Finding: Potential SQL injection vulnerability
Recommendation: Use parameterized queries instead:
   query = "SELECT * FROM users WHERE id = %s"
   cursor.execute(query, (user_id,))

WARNINGS
--------

Location: src/api.py:128
Finding: Function `process_data` exceeds 50 lines
Recommendation: Consider breaking into smaller functions

============================================
Case Status: REQUIRES ATTENTION
============================================

Environment Variables

Variable	Required	Description
OPENAI_API_KEY	Yes	Your OpenAI API key
GITHUB_TOKEN	For PR investigations	GitHub token with PR write access
BENNO_CONFIG	No	Path to custom config file

Development

# Clone repository
git clone https://github.com/bimakw/detective-benno.git
cd detective-benno

# Create virtual environment
python -m venv venv
source venv/bin/activate  # Linux/Mac
# or: venv\Scripts\activate  # Windows

# Install development dependencies
pip install -e ".[dev]"

# Run tests
pytest

# Run linting
ruff check .
mypy src/

Why "Detective Benno"?

Every codebase has mysteries waiting to be solved - bugs hiding in plain sight, security vulnerabilities lurking in the shadows, and performance bottlenecks slowing everything down. Detective Benno is your tireless investigator, examining every line of code to uncover issues before they become problems.

Contributing

Contributions are welcome! Please read our Contributing Guide for details.

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'feat: add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

Acknowledgments

• OpenAI for GPT-4 API
• GitHub Actions for CI/CD integration
• The open source community

---

Detective Benno - Solving code mysteries, one PR at a time
_{Made with code by Bima Kharisma Wicaksana}