智能提交重写工具

🔧 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 models - View available models: omni-dev config models show - Pick per-invocation with the global --model flag, or configure via OMNI_DEV_MODEL / the per-backend env chain (CLAUDE_MODEL, CLAUDE_CODE_MODEL, ANTHROPIC_MODEL for Claude-family backends; OPENAI_MODEL; OLLAMA_MODEL) or ~/.omni-dev/settings.json - 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

folder rule in settings.json permitting the destination

omni-dev drive auth login --write-file # or --write-full to edit omni-dev drive permissions show # what is configured omni-dev drive permissions check <folder-id> --operation create # what it decides omni-dev drive create --name notes.txt --parent <folder-id> omni-dev drive upload ./report.pdf --parent <folder-id> omni-dev drive edit <file-id> --content ./report.pdf # or --content - for stdin ```

An OAuth2 client left in Google's "Testing" publishing status issues refresh tokens that expire after 7 days — see docs/drive.md for how to avoid re-running auth login weekly.

Five read-only MCP tools (drive_*) mirror the CLI's auth status, search, dedupe, read, and account list — see docs/mcp.md. The mutating verbs — rename/move/create/upload/edit — have no MCP equivalent. For the full guide, see docs/drive.md.

⚙️ 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

See the User Guide's Key Options table for the full reference; omni-dev git commit message twiddle --help is the source of truth.

"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

📧 Gmail Integration

Authenticate against your own Gmail account via OAuth2 (loopback authorization-code + PKCE), search/read/label messages and threads, and maintain a durable local archive with gmail sync. New to this integration? Start with the Gmail Quickstart for a zero-to-synced-archive walkthrough; see the Gmail integration guide for prerequisites (you bring your own Google Cloud OAuth2 client — Gmail read scopes require Google's CASA security assessment to distribute otherwise), authentication setup, rate-limit behaviour, and troubleshooting.

```bash

📁 Drive Integration

Authenticate against your own Google Drive account via OAuth2 (loopback authorization-code + PKCE, the same flow as Gmail), then search files, read their metadata or content, find duplicates, rename/move files, and create, upload, or replace file content. Every write is opt-in twice over. First by OAuth scope: the default drive.readonly covers search/read/dedupe; rename/move need drive.metadata (drive auth login --write), the narrowest write scope Google offers; create/upload need drive.file (--write-file); and editing a file omni-dev did not itself create needs the unrestricted drive scope (--write-full). Second by a local, folder-scoped gate: create/upload/edit resolve the target's ancestor folder chain against per-account rules in settings.json — closest ancestor wins, deny beats allow, and a write with no matching rule is denied — so an OAuth grant alone never authorizes a mutation (see ADR-0071). Inspect that gate with `drive permissions show/lookup-folder/check` before granting anything. There is still no trash/share/permission-mutation capability anywhere in this surface. `drive move` is separately security-gated: it refuses any move that would change a file's visibility by default (see ADR-0070). New to this integration? Start with the Drive Quickstart for a zero-to-first-search walkthrough; see the Drive integration guide for prerequisites (you bring your own Google Cloud OAuth2 client, independent of Gmail's), 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), a Snowflake SQL service (one external-browser SSO session reused for concurrent queries), and a worktrees registry (one live view of the repos open across every VS Code window), 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