Features

Proactive Code Analysis

Unlike reactive tools, drep continuously monitors repositories and automatically:

• Detects bugs, security vulnerabilities, and best practice violations
• Opens issues with detailed findings and suggested fixes
• No manual intervention required

Docstring Intelligence

LLM-powered docstring analysis purpose-built for Python:

• Generates Google-style docstrings for public APIs
• Flags TODOs, placeholders, and low-signal docstrings
• Respects decorators (e.g., @property, @classmethod) and skips simple helpers

Automated PR/MR Reviews

Intelligent review workflow for Gitea pull requests:

• Parses diffs into structured hunks
• Generates inline comments tied to added lines
• Produces a high-level summary with approval signal

Flexible LLM Backends

Choose the right LLM backend for your needs:

• Local models: Complete privacy with Ollama, llama.cpp, LM Studio
• AWS Bedrock: Enterprise compliance with Claude 4.5 on AWS ✅ NEW
• Anthropic Direct: Latest Claude models with direct API access (planned)
• OpenAI-compatible: Works with any compatible endpoint

Platform Support & Roadmap

• Available now: Gitea, GitHub, GitLab + Python repositories
• Planned: Additional languages, advanced draft PR workflows

LLM-Powered Analysis

drep includes intelligent code analysis powered by local LLMs via OpenAI-compatible backends (LM Studio, Ollama, open-agent-sdk).

Features

• Code Quality Analysis: Detects bugs, security issues, and best practice violations
• Docstring Generation: Automatically generates Google-style docstrings
• PR Reviews: Context-aware code review comments
• Smart Caching: 80%+ cache hit rate on repeated scans
• Cost Tracking: Monitor token usage and estimated costs
• Circuit Breaker: Graceful degradation when LLM unavailable
• Progress Reporting: Real-time feedback during analysis

Quick Start

Step 1: Install drep

pip install drep-ai

Step 2: Initialize Configuration (Interactive Wizard) 🧙‍♂️

drep init

The interactive wizard guides you through:

1. Config Location: Choose between current directory or user config directory
2. Platform Selection: Gitea, GitHub, or GitLab
3. Enterprise Servers: Detect and configure GitHub Enterprise, self-hosted GitLab/Gitea
4. Repository Patterns: Use wildcards (owner/*) or specific repos (owner/repo)
5. LLM Backend: OpenAI-compatible (local), AWS Bedrock, or Anthropic
6. Documentation Settings: Enable markdown linting, custom dictionaries
7. Advanced Options: Database URL, LLM temperature, rate limits

Example Wizard Flow:

$ drep init

============================================================
Welcome to drep configuration setup!
============================================================

Where should the configuration be created?

  1. Current directory (./config.yaml)
     Use for project-specific configuration

  2. User config directory (/Users/you/Library/Application Support/drep/config.yaml)
     Use for system-wide configuration (recommended for pip/brew install)

Choose location (1, 2) [2]: 1

Step 1: Git Platform Configuration
------------------------------------------------------------
Which git platform are you using? (github, gitea, gitlab) [github]: github

GitHub Configuration:
Are you using GitHub Enterprise? [y/N]: n

Repository Configuration:
Examples: 'your-org/*' (all repos), 'owner/repo' (single repo)
Enter repositories (comma-separated) [your-org/*]: slb350/*

Step 2: LLM Configuration
------------------------------------------------------------
Enable LLM-powered code analysis? [Y/n]: y
Choose LLM provider (openai-compatible, bedrock, anthropic) [openai-compatible]: openai-compatible

OpenAI-Compatible Configuration:
API Endpoint [http://localhost:1234/v1]:
Model name [qwen3-30b-a3b]:
Require API key? [y/N]: n

... (more wizard steps) ...

============================================================
✓ Configuration created successfully!
============================================================

Config location: config.yaml

Next steps:
1. Set the GITHUB_TOKEN environment variable:
   export GITHUB_TOKEN='your-api-token-here'

2. Validate your configuration:
   drep validate

3. Start scanning repositories:
   drep scan owner/repo

Manual Configuration (Alternative)

For advanced users who prefer YAML editing:

Option 1: Local Models (LM Studio)

1. Install LM Studio: https://lmstudio.ai/
2. Download a model (Qwen3-30B-A3B recommended)
3. Create config.yaml:

llm:
  enabled: true
  endpoint: http://localhost:1234/v1  # LM Studio / OpenAI-compatible API (also works with open-agent-sdk)
  model: qwen3-30b-a3b
  temperature: 0.2
  max_tokens: 8000

  # Rate limiting
  max_concurrent_global: 5
  requests_per_minute: 60

  # Caching
  cache:
    enabled: true
    ttl_days: 30

Option 2: AWS Bedrock (Claude 4.5)

1. Enable Bedrock model access in AWS Console
2. Configure AWS credentials (aws configure or ~/.aws/credentials)
3. Configure drep:

llm:
  enabled: true
  provider: bedrock  # Required for AWS Bedrock

  bedrock:
    region: us-east-1
    model: anthropic.claude-sonnet-4-5-20250929-v1:0  # Or Haiku 4.5

  temperature: 0.2
  max_tokens: 4000

  # Caching
  cache:
    enabled: true
    ttl_days: 30

See docs/llm-setup.md for detailed setup instructions and troubleshooting.

Run Analysis

drep scan owner/repo --show-progress --show-metrics

View Metrics

# Show detailed usage statistics
drep metrics --detailed

# Export to JSON
drep metrics --export metrics.json

# Last 7 days only
drep metrics --days 7

Example output:

===== LLM Usage Report =====
Session duration: 0h 5m 32s
Total requests: 127 (115 successful, 12 failed, 95 cached)
Success rate: 90.6%
Cache hit rate: 74.8%

Tokens used: 45,230 prompt + 12,560 completion = 57,790 total
Estimated cost: $0.29 USD (or $0 with LM Studio)

Performance:
  Average latency: 1250ms
  Min/Max: 450ms / 3200ms

By Analyzer:
  code_quality: 45 requests (12,345 tokens)
  docstring: 38 requests (8,901 tokens)
  pr_review: 44 requests (36,544 tokens)

Quick Start

Installation

Via Homebrew (macOS/Linux)

brew tap slb350/drep
brew install drep-ai

Via pip

pip install drep-ai

Note: The PyPI package is named drep-ai (the name drep was already taken). After installation, the command-line tool is still drep.

From source

git clone https://github.com/slb350/drep.git
cd drep
pip install -e ".[dev]"

Via Docker

docker pull ghcr.io/slb350/drep:latest

Configuration

drep supports GitHub, Gitea, and GitLab. The init command will ask which platform you're using and generate the correct configuration.

Step 1: Initialize Configuration

drep init

You'll be prompted to choose where to store the configuration and which platform to use:

Where should the configuration be created?

  1. Current directory (./config.yaml)
     Use for project-specific configuration

  2. User config directory (~/.config/drep/config.yaml)
     Use for system-wide configuration (recommended for pip/brew install)

Choose location (1, 2) [2]: 2

Step 1: Platform Configuration
------------------------------------------------------------
Which git platform are you using?
Choose platform (github, gitea, gitlab) [github]: github

✓ Configuration created successfully!
------------------------------------------------------------
Config location: /Users/yourname/.config/drep/config.yaml

Next steps:
1. Set the GITHUB_TOKEN environment variable:
   export GITHUB_TOKEN='your-api-token-here'

Config File Discovery: drep automatically finds your config file in this order:

1. Explicit --config path (if provided)
2. DREP_CONFIG environment variable
3. ./config.yaml (project-specific)
4. ~/.config/drep/config.yaml (user config)

This means you can run drep scan owner/repo without specifying --config - it will automatically find your configuration!

Step 2: Set Your API Token

Create an API token from your platform:

For GitHub:

1. Go to Settings → Developer settings → Personal access tokens → Tokens (classic)
2. Generate new token with repo scope
3. Set the environment variable:

export GITHUB_TOKEN="ghp_your_token_here"

For Gitea:

1. Go to Settings → Applications → Generate New Token
2. Set the environment variable:

export GITEA_TOKEN="your_token_here"

For GitLab:

1. Go to User Settings → Access Tokens
2. Create token with api scope
3. Set the environment variable:

export GITLAB_TOKEN="your_token_here"

Step 3: Configure Repositories (Optional)

Edit your config file (location shown in drep init output) to specify which repositories to monitor:

# For GitHub:
github:
  token: ${GITHUB_TOKEN}
  repositories:
    - myorg/*           # All repos in 'myorg'
    - myorg/myrepo      # Specific repo

# For GitLab (gitlab.com or self-hosted):
gitlab:
  url: https://gitlab.com  # Or your self-hosted URL
  token: ${GITLAB_TOKEN}
  repositories:
    - myorg/*           # All projects in 'myorg'
    - myorg/myproject   # Specific project

# For Gitea:
gitea:
  url: http://localhost:3000
  token: ${GITEA_TOKEN}
  repositories:
    - myorg/*

Step 4: (Optional) Set Up Local LLM

For AI-powered analysis, you'll need an LLM backend. The init command creates a config with LM Studio defaults:

Option A: LM Studio (Easiest)

1. Download from https://lmstudio.ai/
2. Load a model (Qwen3-30B-A3B recommended)
3. Start the server (default: http://localhost:1234)
4. No config changes needed!

Option B: Ollama

1. Install Ollama from https://ollama.ai/
2. Pull a model: ollama pull qwen3-30b-a3b
3. Update config.yaml:

llm:
  endpoint: http://localhost:11434/v1  # Ollama's OpenAI-compatible endpoint

Option C: AWS Bedrock (Enterprise)

1. Enable Claude models in AWS Console
2. Configure AWS credentials (aws configure)
3. Update config.yaml:

llm:
  provider: bedrock
  bedrock:
    region: us-east-1
    model: anthropic.claude-sonnet-4-5-20250929-v1:0

The default config generated by drep init includes LLM settings for LM Studio. If you don't want AI features, set llm.enabled: false in config.yaml.

Run drep

As a Service (Recommended)

# Start web server to receive webhooks
drep serve --host 0.0.0.0 --port 8000

Configure webhooks to point to:

• Gitea: http://your-server:8000/webhooks/gitea
• GitLab: http://your-server:8000/webhooks/gitlab
• GitHub: http://your-server:8000/webhooks/github

Webhook authentication (Gitea): set a shared secret in your config and the same secret in Gitea's webhook settings — requests without a valid X-Gitea-Signature (HMAC-SHA256 of the raw body) are rejected with 403:

webhook_secret: ${DREP_WEBHOOK_SECRET}

Without a configured secret, webhooks are accepted without authentication (a warning is logged).

Manual Scan

# Scan a specific repository
drep scan owner/repository

Review a Pull Request

# Analyze PR #42 on owner/repository without posting comments
drep review owner/repository 42 --no-post

Docker Compose (with Ollama)

version: '3.8'
services:
  drep:
    image: ghcr.io/slb350/drep:latest
    ports:
      - "8000:8000"
    volumes:
      - ./config.yaml:/app/config.yaml
      - ./data:/app/data
    environment:
      - DREP_LLM_ENDPOINT=http://ollama:11434
    depends_on:
      - ollama

  ollama:
    image: ollama/ollama:latest
    ports:
      - "11434:11434"
    volumes:
      - ollama_data:/root/.ollama

volumes:
  ollama_data:

docker compose up -d

Pre-Commit Integration

drep can run as a pre-commit hook to analyze code locally before commits, without requiring platform API tokens. Perfect for catching issues early in your workflow.

Option 1: Using pre-commit framework

1. Install pre-commit framework:

pip install pre-commit

2. Add drep to your .pre-commit-config.yaml:

repos:
  - repo: https://github.com/slb350/drep
    rev: v0.9.0  # Use the latest version
    hooks:
      - id: drep-check          # Checks only staged files
      # - id: drep-check-all    # OR check all Python files

3. Install the hook:

pre-commit install

Now drep will automatically check your staged files before each commit!

Option 2: Manual git hook

Add to .git/hooks/pre-commit:

#!/bin/bash
drep check --staged

Make it executable:

chmod +x .git/hooks/pre-commit

Pre-Commit Commands

# Check only staged files (pre-commit workflow)
drep check --staged

# Check specific file or directory
drep check path/to/file.py
drep check src/

# Warning mode (don't block commits)
drep check --staged --exit-zero

# JSON output for tools
drep check --format json

Local-Only Config (No Platform Required)

For pre-commit usage, you don't need Gitea/GitHub/GitLab tokens. Create a minimal config.yaml:

# Minimal config for local-only analysis
llm:
  enabled: true
  endpoint: http://localhost:1234/v1
  model: qwen3-30b-a3b

documentation:
  enabled: true

Or disable LLM features entirely:

documentation:
  enabled: true

llm:
  enabled: false  # Use only rule-based checks

The drep check command works without any platform configuration!

How It Works

Repository Scanning

Push Event → drep receives webhook
           ↓
         Scans all files
           ↓
   ┌──────┴──────┐
   ▼             ▼
Doc Analysis        Code Analysis
   ↓                    ↓
Docstring Findings   Code Quality Findings
           ↘          ↙
         Issues / Review Comments

Docstring Analysis (Python)

File → Function extraction → Filtering (public ≥3 lines) → LLM docstring review
                                                    ↓
                                          Suggestions & findings

PR Review

PR Opened → Analyze changed files
           ↓
         Find issues
           ↓
    Post review comments

What drep Detects

Documentation Issues

• Missing docstrings on public functions and methods
• Placeholder docstrings containing TODO/FIXME text
• Generic descriptions that fail to explain purpose or behavior
• Decorated accessors without documentation (@property, @classmethod)
• Optional Markdown checks (when documentation.markdown_checks = true):
  • Trailing whitespace, tabs
  • Empty or malformed headings (e.g., missing space after #)
  • Unclosed code fences (```)
  • Long lines (>120 chars), multiple blank lines, trailing blank lines
  • Bare URLs (suggest wrapping in [text](url)) and basic broken link syntax

Code Issues

• Bare except clauses
• Mutable default arguments
• Security vulnerabilities
• Best practice violations
• Potential bugs
• Performance issues

Supported Languages

• Python (Google-style docstrings)

Additional language support is planned for upcoming releases.

Example Output

Example PR Review Summary

## 🤖 drep AI Code Review

Looks great overall! Tests cover the new behavior and naming is clear.

**Recommendation:** ✅ Approve

---
*Generated by drep using qwen3-30b-a3b*

Example Docstring Suggestion

Suggested docstring for `calculate_total()`:

```python
def calculate_total(...):
    """
    Compute the final invoice total including tax.

    Args:
        prices: Individual line-item amounts.
        tax_rate: Tax rate expressed as a decimal.

    Returns:
        Total amount with tax applied.
    """
```

**Reasoning:** Summarizes the calculation inputs and highlights tax handling.

Configuration

Full config.yaml Example

Option 1: Local LLM (LM Studio / Ollama)

gitea:
  url: http://localhost:3000
  token: ${GITEA_TOKEN}
  repositories:
    - your-org/*

documentation:
  enabled: true
  custom_dictionary:
    - asyncio
    - fastapi
    - kubernetes

database_url: sqlite:///./drep.db

llm:
  enabled: true
  endpoint: http://localhost:1234/v1  # LM Studio / Ollama endpoint
  model: qwen3-30b-a3b
  temperature: 0.2
  timeout: 120
  max_retries: 3
  retry_delay: 2
  max_concurrent_global: 5
  max_concurrent_per_repo: 3
  requests_per_minute: 60
  max_tokens_per_minute: 80000
  cache:
    enabled: true
    directory: ~/.cache/drep/llm
    ttl_days: 30
    max_size_gb: 10

Option 2: AWS Bedrock (Phase 3.3 - Complete) ✅

llm:
  enabled: true
  provider: bedrock

  bedrock:
    region: us-east-1
    model: anthropic.claude-3-5-sonnet-20241022-v2:0
    # Optional: Uses AWS credentials chain if not specified
    # aws_access_key_id: ${AWS_ACCESS_KEY_ID}
    # aws_secret_access_key: ${AWS_SECRET_ACCESS_KEY}

  temperature: 0.2
  max_tokens: 4000
  cache:
    enabled: true

Option 3: Anthropic Direct (Planned - Phase 3.4)

llm:
  enabled: true
  provider: anthropic

  anthropic:
    api_key: ${ANTHROPIC_API_KEY}
    model: claude-3-5-sonnet-20241022

  temperature: 0.2
  max_tokens: 4000
  requests_per_minute: 50  # Anthropic tier limits
  cache:
    enabled: true

Environment Variables

# Platform tokens (recommended over hardcoding)
export GITEA_TOKEN="your-token"
# Future adapters will also respect:
# export GITHUB_TOKEN="your-token"
# export GITLAB_TOKEN="your-token"

# Config file location (part of auto-discovery hierarchy)
export DREP_CONFIG="/path/to/config.yaml"

# Override LLM endpoint (optional)
export DREP_LLM_ENDPOINT="http://localhost:11434"

CLI Commands

All commands auto-discover your config file. Use --config only to override the default discovery.

# Initialize configuration (prompts for location)
drep init

# Validate configuration (auto-discovers config)
drep validate

# Check local files (pre-commit friendly, config optional)
drep check [PATH] [--staged] [--exit-zero] [--format text|json]

# Start web server (auto-discovers config)
drep serve [--host 0.0.0.0] [--port 8000]

# Manual repository scan (auto-discovers config)
drep scan owner/repo

# Review a pull request (auto-discovers config)
drep review owner/repo PR_NUMBER [--no-post]

# View metrics
drep metrics [--detailed] [--export FILE] [--days N]

# Override config file location (any command)
drep scan owner/repo --config /path/to/config.yaml

Architecture

drep uses a modular architecture with platform adapters:

drep/
├── adapters/         # Platform-specific implementations
│   ├── base.py       # Abstract adapter interface
│   ├── gitea.py      # Gitea adapter
│   ├── github.py     # GitHub adapter
│   └── gitlab.py     # GitLab adapter
├── core/             # Core business logic
├── documentation/    # Documentation analyzer
└── models/           # Data models

See docs/technical-design.md for complete architecture details.

Development

Setup Development Environment

# Clone repository
git clone https://github.com/slb350/drep.git
cd drep

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

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

# Run tests
pytest

# Format code
ruff format drep/
ruff check drep/

# Type checking
mypy drep/

Running Tests

# Run all tests
pytest

# Run with coverage
pytest --cov=drep --cov-report=html

# Run specific test file
pytest tests/unit/test_adapters.py

Roadmap

See docs/roadmap.md for the complete development roadmap with priorities, timelines, and contribution opportunities.

Current Status (v1.0.0 - Production Release) 🎉

• ✅ Full platform support: Gitea, GitHub, and GitLab
• ✅ Complete BaseAdapter implementation for all platforms
• ✅ LLM-powered code quality analysis (Python)
• ✅ Pre-commit hook support (local-only analysis)
• ✅ Intelligent caching (80%+ hit rate)
• ✅ Circuit breaker & rate limiting
• ✅ Docstring generator for Python
• ✅ CLI interface with metrics tracking
• ✅ 618 tests passing (production-ready)

Development Progress (5 Development Phases)

🎯 Phase 1: Quick Wins (Sprint 1-2) ✅ COMPLETE

• Security audit, BaseAdapter interface, extract constants
• 22 new tests added, 390 total tests passing

🔧 Phase 2: Quality & Testing (Sprint 3-4) ✅ COMPLETE

• E2E integration tests, API documentation, dependency injection
• 18 new tests added, 411 total tests passing

🚀 Phase 3: Platform & LLM Backend Expansion (Sprint 5-8) ✅ COMPLETE

• ✅ Phase 3.1: GitHub adapter (API complete, 58 unit + 6 integration tests)
• ✅ Phase 3.2: CLI integration for GitHub (scan & review commands)
• ✅ Phase 3.3: AWS Bedrock LLM provider (Claude 4.5, enterprise compliance, 17 tests)
• ✅ Phase 3.5: GitLab adapter support (API complete, 93 unit tests)
• ✅ Phase 3.6: Pre-commit hook support (local-only analysis, 14 tests)
• 🔜 Phase 3.4: Anthropic Direct LLM provider (planned, latest Claude models)

🌟 Phase 4: Feature Expansion (Sprint 9-12)

• Multi-language support (JavaScript, TypeScript, Go, Rust)
• Web UI dashboard for viewing findings and metrics

🔬 Phase 5: Advanced Features (Backlog)

• Custom rules engine, performance optimizations, vector database for cross-file context

Want to help? Good first issues: Anthropic Direct provider, adding benchmarks, multi-language support. See docs/roadmap.md for details.

Comparison with Existing Tools

Feature	drep (current)	Greptile	PR-Agent	Codedog
CLI repository scans	✅	❌	❌	❌
Docstring suggestions (Python)	✅	❌	❌	❌
Gitea PR reviews	✅	❌	❌	❌
Local LLM	✅	❌	Partial	Partial
Gitea support	✅ Full	❌	❌	❌
GitHub support	✅ Full	✅	✅	✅
GitLab support	✅ Full	✅	✅	✅
Draft PR automation	🚧 Planned	❌	❌	❌

Key Differentiator: drep is the only tool with full support for Gitea, GitHub, AND GitLab, powered by local LLMs for complete privacy. Perfect for organizations using multiple git platforms or self-hosted solutions.

Contributing

Contributions are welcome! Please see CONTRIBUTING.md for guidelines.

License

MIT License - see LICENSE for details.

Support

• Documentation: docs/
• Issues: https://github.com/slb350/drep/issues
• Discussions: https://github.com/slb350/drep/discussions

Acknowledgments

• Uses OpenAI-compatible local LLMs (LM Studio, Ollama)
• Inspired by tools like Greptile, PR-Agent, and Codedog
• Thanks to the open-source community

---

Made with ❤️ for developers who care about code quality and documentation