Git-surgeon gives AI agents surgical control without interactive prompts
Git-surgeon is a tool that enables AI agents to manage git changes without needing interactive prompts. It allows for precise control over commits, including staging, unstaging, and discarding individual hunks. This functionality helps avoid destructive workarounds that agents previously had to use when committing changes separately.
- ▪Git-surgeon allows AI agents to stage, unstage, or discard individual hunks of code.
- ▪The tool enables agents to commit hunks directly with line-range precision.
- ▪Git-surgeon can restructure commit history by splitting or folding commits.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,275 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/raine/git-surgeon |
| Publication time | Sun, 17 May 2026 20:45:16 +0000 |
| Retrieval time | 2026-05-17T20:53:20.964Z |
| Last seen | 2026-05-17T20:53:20.964Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | kpoQKA6fT0O7 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
git-surgeon Install · Commands · Examples · Changelog git-surgeon gives AI agents surgical control over git changes without interactive prompts. Stage, unstage, or discard individual hunks. Commit hunks directly with line-range precision. Restructure history by splitting commits or folding fixes into earlier ones. Check out jj-hunk-tool if you're using Jujutsu. Why? AI agents can't use interactive git commands like git add -p. When asked to commit changes separately, they resort to destructive workarounds: ❯ commit the changes separately ⏺ Bash(git diff internal/bot/listing_handler.go) ⎿ diff --git i/internal/bot/listing_handler.go ... ... +83 lines ⏺ Let me reset and make the changes in two separate commits.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.