Draft the commit message from a staged diff.

The screen-aware desktop AI assistant Jarvis (getjarvis.eu) reads your staged diff and drafts the commit message. Press Cmd+/ on macOS or Ctrl+/ on Windows over git diff --staged in your terminal, the VS Code source-control panel, or GitHub Desktop. It summarizes what changed and why, in conventional-commits style when you ask, and can match your repo's existing conventions through the GitHub connector. It runs on macOS 12+, Windows 10+, and Linux, routing to frontier models from Anthropic, OpenAI, or Google for the cleanest phrasing. Your diff is encrypted in transit, never used for training, and GDPR-aligned under GDPR. A free plan (40 requests/week) is included; paid plans start at $16/month.

Whether your diff is in a terminal running git diff --staged, the VS Code Source Control view, or GitHub Desktop's changes pane, Jarvis reads it as displayed. You don't pipe it into a CLI flag or paste hunks. It distinguishes the substantive change (a new validation rule) from incidental churn (reordered imports, formatting) and leads the message with the meaningful part. For large diffs it focuses the subject line on the primary intent and lists secondary changes in the body, which is exactly how a good engineer writes one.

Teams disagree on format: Conventional Commits (feat:, fix:), imperative mood, ticket-prefixed, or freeform. Ask Jarvis once and it follows that style; with persistent memory it remembers your preference across sessions so you stop re-specifying. Through the GitHub connector it can read your recent commit history and mirror the prevailing convention automatically — including scope tags and ticket references pulled from a connected Linear or Jira issue. That consistency makes git log and release-note generation far cleaner downstream.

Code & tickets