GitBorGitBor

AI Helpers

Commit Explainer, Smart Stash Naming, Reflog Explainer, Conflict Helper and Semantic Search

Beyond commit messages, GitBor has five AI helpers. They share the provider, prompts and privacy settings of the AI commit-message generator — set those up first.

What they all have in common:

  • The instruction text for each one lives in the Prompts tab of AI Settings (English by default; the response language is separate).
  • Each can be toggled in the Features tab; a disabled helper hides its button.
  • On a foreign provider with the privacy switch off, the helper simply doesn't run.
  • Where it makes sense, the answer streams into the panel; a second click on the same button cancels the request.
  • Every explanation carries a reminder that AI output may be inaccurate — always verify the code.

Commit Explainer

An Explain commit button in the Commit Details panel. It writes a short, high-level summary (what changed, why, what to watch out for) — not a line-by-line walk-through. Useful when reviewing a pull request, scanning an old release, or reading a merge commit.

Smart Stash Naming

The stash dialog has a Suggest name button. It looks at your uncommitted changes and proposes a short name (lowercase, no quotes). Click again to regenerate; the field stays fully editable — Suggest only seeds it. The language follows your AI response-language setting.

Reflog Explainer

An Explain reflog button in the Reflog dialog turns raw git reflog lines into a readable timeline: it groups low-level actions into one logical event, flags moments where HEAD moved without a commit (the recoverable "lost" commits), and suggests the exact recovery command when something looks like a mistake.

Conflict Helper

An Explain conflict button in the merge editor toolbar. It does not resolve the conflict — it explains it: what each side (Ours / Theirs) changed in the selected hunk, why where the code makes it clear, and what to consider before picking a side. You stay in control of every keystroke.

The commit-graph search (Ctrl+F) has an AI toggle (not the same as regexp — the modes exclude each other). Turn it on and describe the query in plain language:

what changed in indexing this week
feature flag for the new editor

An ai: text prefix is not required and not supported — use the toggle only.

GitBor sends a recent history slice (subject and body) to your model and asks it to pick commits by meaning. You get the same filtered list as plain search.

This is the first, simplified version: no vector embeddings yet, so only the most recent N commits are visible. Full-history indexing is on the roadmap.

When things go wrong

  • A second click on an active helper button cancels the request.
  • Provider errors (rate limit, auth, network) appear inline in the same panel and don't block the rest of the UI.
  • If a reply looks off, the Debug tab of AI Settings shows exactly what GitBor sent and received.