BeeTool.Dev - Essential Tools for developers

Stories.Tool Tabs VaultPersonal Documents
BeeTool.Dev

Essential tools, knowledge, and playgrounds for developers.

Explore

  • Stories
  • Personal Documents
  • Features
  • Beetool for Mac
  • Algorithms Playground

Tool Tabs

  • JSON Compare
  • SQL Formatter
  • Text Diff
  • All tools →

Learn

  • Sorting algorithms
  • Searching algorithms
  • Algorithm Race Mode
© 2024 – 2026 BeeTool.Dev
AboutContactPrivacy policyTerms
ContentsDocumentation home

Get started

  • What is Beetool
  • Install & first launch
  • Projects, workspaces & navigation
  • Keyboard shortcuts

AI

  • AI assistant
  • AI providers & models
  • Knowledge & project context
  • Agent teams
  • AI usage & run ledger
  • MCP server

Code & Git

  • Code editor
  • Run, test & debug
  • Terminal
  • Git
  • Merge requests
  • AI review & rule sets

Work

  • Beework tasks & board
  • Products
  • Docs & AI Docs

Tools

  • Database
  • Beequest — HTTP client
  • SSH, SFTP & Vault
  • Processes & network
  • Text files

Reference

  • Settings
  • Privacy & data

Code & Git

Git

Commit, branch, sync and dig through history — plus visual tools for the git commands people look up every time.

Beetool uses your installed git; no token is needed for local work.

#Commit and sync

The Changes panel (Git sidebar or Code's right panel) stages, unstages and discards per file or all at once, commits or amends, pushes and pulls.

  • Write message drafts a commit message from your changes, in the repository's style.
  • Split into commits lets AI group your changes into small commits — you check the plan first.
  • Review my changes reviews your branch and uncommitted work like a merge request.
  • Sync fetches everything and fast-forwards the current branch only when that is safe. It never merges, rebases or overwrites local work, and tells you why when it can't.

#History, blame and trace

  • History — commit graph across branches or per file, commit details, filters by author, message and date, and git log -S search. Explain history writes a summary for someone new to the code.
  • Files & blame — a file's timeline across renames. Compare diffs any two revisions; File shows the file at a revision with blame.
  • Trace lines (⇧⌘T) — every commit that touched the selected lines, each linked to its merge request.

#Git tools

ToolWhat it does
Undo & reflogEverything HEAD did; take back a commit, reset, rebase, merge or switch
ConflictsAccept current, incoming or both — per conflict or file — or ask AI
Rearrange commitsSquash, reword, reorder, drop
Stage linesStage or discard single lines and hunks
StashesLook inside, apply, pop, branch, create
Tags & releasesAnnotated tags, push, AI release notes
BisectFind the commit that broke it, optionally with a test command
Branch cleanupMerged and gone branches
Submodules & LFSStatus, update, pull
Cherry-pick an MRTry an open merge request on another branch

#Conflicts

The conflict view tints each conflict, explains it in plain words and suggests a one-click fix when it is safe ("only reformatted"). The merge editor shows current, result and incoming side by side, with clean changes already applied; F7 / ⇧F7 move between conflicts and Resolve with AI proposes a result. Continue, skip or abort the merge, rebase or cherry-pick from the same screen.

PreviousTerminalNext Merge requests

On this page

  • Commit and sync
  • History, blame and trace
  • Git tools
  • Conflicts