Agent skill · software engineering · code-yeongyu
git-master
MUST USE for ANY git operations: atomic commits, rebase/squash/fixup, and history search (blame, bisect, log -S, reflog). Load it before running git yourself, or pass load_skills=['git-master'] to the task that commits. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
Why this skill is useful
Adds specific git commands and workflows for managing commit history and styles that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 67,387 stars on the source repository.
What this skill does
Git Master Use this skill when the user asks you to operate on Git history or answer a Git-history question. Be exact, conservative, and evidence-led. Read the repository state before you infer anything. Mode Gate Classify the request first: COMMIT: stage and commit local changes. REBASE: rebase, squash, fixup, autosquash, reorder, split, or otherwise rewrite branch history. HISTORY: answer when, where, who, why, or which commit changed something. STATUS: inspect branch, diff, or working-tree state without changing it. Do not commit, rebase, push, force-push, reset, stash-pop, or delete anything unless the user explicitly asked for that operation. When a workflow the user started mandates one of them (ulw-loop commits each verified unit, ulw-execute lands its branches), that workflow's instruction is the ask. If the request is only investigative, report findings and stop. Ground Truth Gather independent facts in parallel when the tools allow it: Missing upstream or missing main/master is normal. Fall back to the best available branch or report the missing fact. Never treat a failed lookup as proof. PR Body Evidence Attachments When a PR body needs screenshots or terminal PNGs, the allowed hosting path is GitHub user attachments from the authenticated web attachment flow; never commit temporary images, never use GitHub Releases for PR evidence, and never use external image hosts. Do not log browser cookies, CSRF tokens, S3 form fields, or upload headers. The flow needs an authenticated GitHub web session (a gh API token alone is not enough): 1. Open the target PR or issue page in that session and read its file-attachment CSRF token and repository id. 2. POST https://github.com/upload/policies/assets with repositoryid, name, size, contenttype, and that token as authenticitytoken. 3. Upload the bytes to the returned S3 URL with the returned form fields exactly as given. 4. PUT https://github.com/upload/assets/:id with the returned assetuploadauthenticitytoken. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills code-yeongyu/git-master--0d99b0