智能提交重写工具

🔧 Requirements

- Rust: 1.80+ (for installation from source) - Claude API Key: Required for AI-powered features - See Authentication for setup (env var, .env, or CI/CD secrets) - AI Model Selection: Optional configuration for specific Claude models - View available models: omni-dev config models show - Configure via ~/.omni-dev/settings.json or ANTHROPIC_MODEL environment variable - Supports standard identifiers and Bedrock-style formats - Atlassian Credentials (for JIRA/Confluence features): Instance URL, email, and API token - Configure with: omni-dev atlassian auth login - Datadog Credentials (for Datadog features): API key, application key, and site - Configure with: omni-dev datadog auth login - Git: Any modern version

Installation

```bash

Install from crates.io

cargo install omni-dev

Install with Nix

nix profile install github:rust-works/omni-dev

Install with Nix flakes (development)

nix run github:rust-works/omni-dev

**Next step:** see [Getting Started](docs/getting-started.md) — a
10-minute walkthrough from authentication to your first AI-improved
commit. (For just the API-key reference, see
[Authentication](docs/configuration.md#authentication).)

#### Shell Completion

`omni-dev completions <shell>` prints a completion script to stdout for
`bash`, `zsh`, `fish`, `powershell`, or `elvish`. The quickest path is bash
per-user:

Start the background daemon (installs a launchd LaunchAgent on macOS)

omni-dev daemon start

Development Setup

1. Clone the repository:

   git clone https://github.com/rust-works/omni-dev.git
   cd omni-dev
   

1. Install Rust (if you haven't already):

   curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
   

1. Build the project:

   cargo build
   

1. Run the build script (includes tests, linting, and formatting):

   ./scripts/build.sh
   

Or run individual steps:

   cargo test         # Run tests
   cargo clippy       # Run linting
   cargo fmt          # Format code
   

🚀 Quick Start

Project Commit Guidelines

📖 Real-World Examples

30-Second Demo

Transform your commit messages and create professional PRs with AI intelligence:

```bash

Configure Datadog API credentials (prompts for API key, APP key, and site)

omni-dev datadog auth login

⚙️ Configuration Commands

```bash

Project Configuration

Create .omni-dev/ directory in your repo root:

mkdir .omni-dev

Scope Definitions (.omni-dev/scopes.yaml)

scopes:
  - name: "auth"
    description: "Authentication and authorization systems"
    examples: ["auth: add OAuth2 support", "auth: fix token validation"]
    file_patterns: ["src/auth/**", "auth.rs"]
  
  - name: "api"
    description: "REST API endpoints and handlers"  
    examples: ["api: add user endpoints", "api: improve error responses"]
    file_patterns: ["src/api/**", "handlers/**"]

Commit Guidelines (.omni-dev/commit-guidelines.md)

```markdown

Command Options

"docs(api): add comprehensive endpoint documentation"

Verify the credentials by calling /api/v1/validate

omni-dev datadog auth status

Stream a long-lived endpoint (SSE / chunked) instead of buffering.

omni-dev browser bridge request --url /api/events --stream

📝 Atlassian Integration

Read, write, and manage JIRA issues and Confluence pages from the command line:

```bash

📊 Datadog Integration (read-only)

Authenticate against the Datadog API and query metrics, monitors, dashboards, logs, events, SLOs, hosts, and downtimes. See the Datadog integration guide for the full subcommand reference, authentication setup, rate-limit behaviour, and troubleshooting.

```bash

Workflow Integration

```bash

Enable debug logging for omni-dev components

RUST_LOG=omni_dev=debug omni-dev git commit message twiddle ...

Debug specific modules (e.g., context discovery)

RUST_LOG=omni_dev::claude::context::discovery=debug omni-dev git commit message twiddle ...

🆚 How omni-dev Compares

omni-dev sits in two adjacent spaces — AI commit-message tooling and Atlassian/dev-workflow MCP servers. The tables below contrast the incumbents on the dimensions a first-time reader is most likely to weigh. In every cell, ✅ means full / native support, ⚠ means partial or available only with caveats, and ❌ means not supported — and omni-dev's own limitations are flagged just as honestly (the ⚠ marks in its own columns).

Beyond these two niches, omni-dev also ships a supervised daemon that hosts a browser bridge (an authenticated proxy that runs requests through a logged-in browser tab for SSO-gated dashboards such as Grafana and Loki) and a Snowflake SQL service (one external-browser SSO session reused for concurrent queries), plus a local append-only request log (omni-dev log). These have no direct incumbent in either table below, so they are called out here rather than scored against tools that don't aim for them.

vs AI commit tools

vs Atlassian-workflow MCP servers

omni-dev's MCP server also exposes Git tools (commit analysis, twiddling, PR creation), Datadog tools, and an ai_chat proxy — surfaces the Atlassian-focused servers don't aim for. The table below compares only Atlassian capability depth.

_Last verified: 2026-06-23. omni-dev and sooperset rows are live-tested — a tools/list enumeration (omni-dev branch build vs ghcr.io/sooperset/mcp-atlassian:latest) plus a live read→write→read fidelity cycle on a complex page. Atlassian Rovo's server accepts the API token but gates tool execution behind an org-admin grant, so its rows combine Atlassian's Supported tools docs with the ADF-passthrough reasoning (raw ADF can round-trip, but only if the model echoes it faithfully — no deterministic guarantee), not a live run. Refresh quarterly or whenever a release-note search for the comparators flags a relevant change.

Analyze current branch vs main

omni-dev git branch info main