A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
3 ★ · rust-works/omni-dev · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 3 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository rust-works/omni-dev;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
An intelligent Git commit message toolkit with AI-powered contextual intelligence. Transform messy commit histories into professional, conventional commit formats with project-aware suggestions. 🎬 See It In Action *Watch omni-dev transform messy commits into professional ones with AI-powered analysis* 30-Second Demo Transform your commit messages and create professional PRs with AI intelligence: ✨ Key Features - 🤖 **AI-Powered Intelligence**: Claude AI analyzes your code changes to suggest meaningful commit messages and PR descriptions - 🧠 **Contextual Awareness**: Understands your project structure, conventions, and work patterns - 🔍 **Comprehensive Analysis**: Deep analysis of commits, branches, and file changes - ✏️ **Smart Amendments**: Safely improve single or multiple commit messages - 🚀 **PR Creation**: Generate professional pull requests with AI-powered descriptions - 📦 **Automatic Batching**: Handles large commit ranges intelligently - 🎯 **Conventional Commits**: Automatic detection and formatting - 🌐 **Browser Bridge**: Drive HTTP requests through an authenticated browser tab without exfiltrating cookies or tokens - 🗂️ **Worktrees View**: One live view of every repo and git worktree open across all your VS Code windows - 🛡️ **Safety First**: Working directory validation, protection against amending commits already in remote main branches, and error recovery - ⚡ **Fast & Reliable**: Built with Rust for memory safety and performance 🚀 Quick Start Installation Pre-built binaries are attached to each release. The Linux ones (omni-dev-linux.tar.gz, omni-dev-linux-arm64.tar.gz) are dynamically linked and need **glibc 2.35 or newer** (Ubuntu 22.04 and Debian 12 qualify). On an older host, such as RHEL 9 or Amazon Linux 2023 (glibc 2.34), they fail in the loader with version GLIBC_2.xx' not found; build from source with cargo install omni-dev instead. The release workflow fails if a binary needs more than that floor (docs/RELEASE.md). **Next step:** see Getting Started — a 10-minute walkthrough from authentication to your first AI-improved commit. (For just the API-key reference, see Authentication.) Shell Completion omni-dev completions prints a completion script to stdout for bash, zsh, fish, powershell, or elvish. The quickest path is bash per-user: See docs/shell-completion.md for per-shell install recipes, the $fpath/compinit setup zsh requires, and troubleshooting. 🆚 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 | | omni-dev | opencommit | aicommits | |-------------------------------------------------------|-------------------------------------|---------------------------------------------------------|---------------------------------------------------| | Rewrite existing commits in a range | ✅ twiddle | ❌ pre-commit only | ❌ pre-commit only | | Parallel batched processing (long ranges) | ✅ --concurrency N | ❌ | ❌ | | AI-written PR descriptions | ✅ git branch create pr | ⚠ GitHub Action only | ❌ | | Project-context awareness | ✅ --use-context | ❌ | ❌ | | Sandboxed claude-cli backend | ✅ ADR-0028 | ❌ | ❌ | | Multi-backend (Anthropic / Bedrock / OpenAI / Ollama) | ✅ | ✅ | ✅ | | Conventional Commits | ✅ | ✅ | ⚠ config | | Language / runtime | Rust (static binary) | Node.js | Node.js | 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