Borrowing it
Nothing to install: this file belongs to lanegrid/agtrace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lanegrid/agtrace/main/.claude/skills/git-workflow/SKILL.mdgit clone --depth 1 https://github.com/lanegrid/agtraceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/lanegrid/agtrace/git-workflow)<a href="https://agentmods.dev/skills/lanegrid/agtrace/git-workflow"><img src="https://agentmods.dev/badge/skills/lanegrid/agtrace/git-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lanegrid/agtrace/git-workflow"><img src="https://agentmods.dev/badge/skills/lanegrid/agtrace/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.02001 |
| Opus 5.5 | $0.00012 | $0.00800 |
| Sonnet 5.5 | $0.00006 | $0.00400 |
| Haiku 4.5 | $0.00003 | $0.00200 |
Grade A, and why
git-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow and Conventions
Worktree-aware Git workflow using mise run git:* tasks.
Quick Reference
# Basic operations
mise run git:status # Show current state + next action
mise run git:home # Switch to home branch + sync with origin/main
mise run git:new <branch> # Create new branch from origin/main
mise run git:cleanup [branch] # Delete merged branch + return to home
# PR lifecycle (CI wait -> browser open -> merge watch -> cleanup)
mise run git:open-pr <pr#> # All-in-one: CI -> open -> watch -> cleanup
# Pause / discard / undo
mise run git:pause [message] # WIP commit + return to home (for switching tasks)
mise run git:abandon # Discard all changes + return to home
mise run git:undo # Soft reset HEAD~1 (undo last commit)
# Stacked PRs
mise run git:sync # Sync current branch after base PR merge
Note: These tasks use the
gwRust CLI (crates.io). Install withcargo install git-workflow.
Pitfalls
- Do not run
git checkout main— usemise run git:homeinstead (worktree conflict)- Do not use
git stash— usemise run git:pauseinstead (creates WIP commit for safer worktree switching)- Do not manually rebase stacked PRs — use
mise run git:syncinstead (updates GitHub PR base + rebases)
Standard Workflow: Code -> PR
Every code change should become a PR. Follow this flow:
1. Branch -> mise run git:new -- feature/your-feature
2. Code -> make changes
3. Commit -> git add -A && git commit -m "feat: ..."
4. Push -> git push -u origin feature/your-feature
5. PR -> gh pr create -a "@me" -t "feat: ..."
6. Open -> mise run git:open-pr <pr#> (CI wait -> browser -> merge watch -> cleanup)
⚠ Run ONCE after final push. If CI fails, stop watcher -> fix -> push -> relaunch.
7. Cleanup -> (auto: merge detected -> git:cleanup runs)
git:open-pr — PR Lifecycle Management (Claude Code Background Task)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 230 lines · 31 tokens per session scan A baa766c74840
git-workflow is a skill published in the GitHub repository lanegrid/agtrace (62 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 2,001 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
commit-staged
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
cuga-contributor-workflows
Run CUGA contributor workflows: Conventional Commits, create pull requests against origin with gh and PR templates, ruff check/format via uv, and the required design-impact, area, and readability labels before every push and pull request. Use when the user says commit, create a commit, push, create PR, pull request…