GitAmp

GitAmp amplifies Git in VS Code with searchable history, a commit graph, revision comparisons, and explicitly guarded actions. It complements native Source Control.

GitAmp is licensed under the MIT License. Third-party components retain their own licenses in THIRD_PARTY_NOTICES.md. See the illustrated user guide for workflows and the changelog for version history.

• Paged, virtualized history with message, author, literal code, and regex code searches; full-day date filters, saved queries, file rename tracking, and matching-change navigation.
• Commit details with merge-parent selection, file statistics, branch/tag/worktree navigation, and readonly historical text/binary resources in native VS Code Diff and Multi Diff.
• Compare version endpoints, branch changes from their common ancestor, the staging area, or tracked working-tree files; start from Quick Compare… (branch changes, unpushed/unpulled, uncommitted, staged), limit a comparison to one file or folder, inspect the commit range, swap sides or pick another branch, tag or commit for either side, walk the changed files from GitAmp Comparison Files in Source Control (previous/next file, viewed marks), and export bounded diff/patch or spreadsheet-safe CSV.
• A constant panel frame: a left rail switches views in place; a one-line command bar turns author:, code:, path:, branch:, since: and is:merge into removable filter chips; uncommitted changes appear as the first graph row; changed files show as a tree or list.
• Operation plans before cherry-pick, revert and checkout: the exact command, effects, checks, predicted conflicts (git merge-tree, Git 2.40+) and how to undo. Resets keep native confirmations; pending-operation handoff and confirmation-time state checks remain.
• An Undo center for HEAD movements, grouped by action: undo a whole rebase, amend, reset or commit with git reset --keep, or verify a completed rebase in one click. The status bar offers Undo after a recent rewrite.
• Trace selected committed lines, recover available commits from local HEAD reference history on a new branch, and compare rewritten commit series with readonly native patch Diff.
• Copy explanation, Code review and Security review tasks for immutable Git changes. Each action reveals existing native Copilot Chat and copies pinned revisions with any configured Skill/custom prompt. Paste, choose a model, review and send there. Preserve existing drafts/attachments, with no automatic new chat, file picker, submission, GitAmp model picker/result panel, key store or provider HTTP integration. Explicit copies use the system clipboard and its normal OS history/sync rules.
• Six readonly Copilot Agent tools for the selected historical scope, changed files, endpoint diffs, file content, history and blame. Reuse complete view metadata and page bounded evidence without a manual file picker. Four existing tools provide repository/commit context and confirmed branch/tag creation, plus session-only investigation summaries for @gitamp without patches or file contents.
• Optional Azure Boards work-item selection and branch associations, with VS Code Microsoft sign-in and explicit service queries. Real tenant access depends on the account and organization configuration.
• Native VS Code integration: a GitAmp status bar entry (gitamp.ui.showStatusBarEntry), right-click entries on editor tabs, line numbers, Source Control changes and Timeline; Ctrl+K Ctrl+G (⌘K ⌘G) shortcuts; Go to Branch, Tag or Commit…; and a panel that reopens after reload with the same repository, filters, view and selection.
• English and Traditional Chinese, VS Code themes, local Codicons, and keyboard navigation (? in the panel lists every shortcut).

Native VS Code Git owns staging, commit composition, remote authentication and synchronization, and conflict resolution. GitAmp also offers explicitly guarded local branch/tag, stash, worktree, merge and rebase actions through its operation plans and native confirmations; fetch uses the native Git API. Conflict prediction runs an in-memory merge only; it never changes refs, the index or files, and it is off for repositories that configure custom merge drivers. GitAmp performs local Git operations through structured argv arrays with separate read/mutation allowlists, cancellation, timeout, and output limits. Activation does not discover repositories or run Git; discovery starts when the view, a command, a tool, or a panel restored after a reload requests it.

Open GitAmp: Open Git History from the Command Palette, Source Control toolbar, repository menu, Explorer, or editor. GitAmp's navigation view lives inside Source Control.

GitAmp lazily uses native Git repository discovery and follows external branch, commit, and ref changes. File history is available from Explorer and editor menus; named searches are stored per repository in workspace state. Staging-area previews use immutable Git object IDs. Working-tree comparisons exclude untracked files; symlink and submodule working previews use native Source Control. Files flagged assume-unchanged or skip-worktree block operations that may overwrite tracked files.

Comparison ranges show up to 200 commits; Multi Diff opens up to 500 files. Revision content is capped at 5 MiB per file. Mutable comparisons must still match their recorded state before export. Changes CSV includes comparison mode and target kind; mutable targets have an empty target SHA.

Select committed lines in the editor and run GitAmp: Show History for Selection. Unsaved or uncommitted file changes must be committed first, or use a readonly historical file. The Undo center (GitAmp: Open Undo Center) previews the actual commit recorded before a local reference movement and creates a new branch after native confirmation. Recovery requires file-based Git reference storage; it reads at most 1 MiB of the current worktree's HEAD log and shows up to 100 movements. Missing objects are unavailable, and unsupported or incomplete logs cannot provide recovery targets. Recovery does not restore uncommitted or pruned content. Compare Rewritten Commit Series takes an old base/tip and new base/tip, each with at most 200 commits and no merges. Pairing is heuristic; inspect the actual patches. Branch, tag and SHA inputs are supported.

Install

Search for GitAmp in the VS Code Extensions view and select Install. To install a VSIX manually, use Extensions: Install from VSIX. GitAmp requires Git on PATH, a trusted workspace, and VS Code matching the manifest engine range. Chat handoff requires GitHub Copilot Chat enabled in VS Code. Choose and configure models, including supported BYOK providers, in native Chat; account, credentials, consent and quota follow VS Code/provider rules.

Development and validation

npm ci
npm run check
npm run test:visual
npm run test:vscode
npm run package
npm run audit:vsix -- gitamp-X.Y.Z.vsix

Git service tests use disposable local repositories and real Git. Browser tests verify geometry and interaction with synthetic messages. Extension Host tests verify activation, native revision/Diff integration, CSP loading, and renderer retention. Fixture tests do not prove official BYOK/Copilot provider access, real model behavior or marketplace installation. Opt-in API/prompt checks remain separate from VS Code BYOK end-to-end validation.

Replace X.Y.Z above with the exact package version. See the user guide, privacy, contribution guidelines, support, security reporting, and release steps.