Add Repo object layer, fastgit.skill pyskill, and non-interactive git - #10
Draft
ncoop57 wants to merge 2 commits into
Draft
Add Repo object layer, fastgit.skill pyskill, and non-interactive git#10ncoop57 wants to merge 2 commits into
ncoop57 wants to merge 2 commits into
Conversation
ncoop57
marked this pull request as draft
July 26, 2026 21:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an object-oriented layer over the raw
Gitverbs, plus a pyskill documenting it for LLM agents.Repo: commits, refs, status, diffs, merges, rebases, stashes, blame, and remotes as live Python objects with terminal-style reprs (--onelinelog,branch -vv,status -sb,--stat)Status; conflicted entries expose.stagesand:1:/:2:/:3:content for resolutionb - aspellsgit diff a b;blame/tracesharefunc=/lines=/regex=range keywordsfastgit.skillregistered as a pyskills entry point, including guidance that agents must never push (let alone force-push) without the user explicitly requesting that specific pushcallgitnow runs git non-interactively (GIT_EDITOR/GIT_SEQUENCE_EDITORsuppressed): with captured output an editor can never function, so commands that would open one (e.g.rebase --continueafter conflict resolution) previously hung forever; tested viagit var GIT_EDITORNotes