Stage, unstage, and discard git hunks non-interactively using stable IDs.
npx skills add https://github.com/jfmyers9/agent --skill git-surgeon-jfmyers9
Please help me install this Agent Skill. Skill: git-surgeon Source: https://github.com/jfmyers9/agent/tree/main/skills/git-surgeon Command: npx skills add https://github.com/jfmyers9/agent --skill git-surgeon-jfmyers9
Non-interactive hunk-level staging, unstaging, and discarding using standard git commands and shasum for hunk identification.
git diff output to generate a short, stable ID per hunk along with file path and a preview.Ask it to list hunks, then stage or discard a selected hunk.
High-intent search queries and answers about installing and using this skill.
You can stage individual git hunks non-interactively by listing them via @@ headers to generate stable short IDs, then explicitly applying the selected ID to the git index. This enforces safety by requiring a list-and-apply confirmation step before staging.
Discarding specific git hunks without reverting the entire file requires parsing the diff output to identify target hunks by their stable short IDs, then executing a targeted revert operation. This destructive action requires an explicit list-and-confirm workflow to prevent accidental data loss.
Yes, unstaging individual hunks from a staged git diff works by reverse-applying the selected hunk ID to the index. The tool resolves patch collisions and uses shasum to ensure the targeted hunk is accurately removed from staging without resetting the entire file.
Non-interactive hunk staging identifies hunks by parsing @@ headers from git diff output and generating stable short IDs using shasum. It resolves collisions automatically, ensuring accurate patch control across single files and multiple hunks in both staged and unstaged states.
No, you do not need interactive mode to preview and apply targeted git patches. You can request a hunk list to display the full content and preview for a given ID, then apply or discard it on demand across multiple files using standard git commands.
Explicit list-and-apply steps are required before discarding git hunks to enforce operational safety. Re-listing the short IDs confirms the exact targets before any destructive patch reversal occurs, preventing accidental loss of unstaged working tree changes.
whatevertogoGenerate standardized Git commit messages from staged and working tree changes.
tobihagemannCommit staged changes and push them to the current branch's remote.
Soyio-idCreate logically scoped git commits with Conventional Commit messages from working-tree changes.
rcdaileyStage specific Git hunks by stable ID for atomic commits.