git-engineer

An agent for coordinating Git workflows such as commits, rebases, pull requests, and branch maintenance. A rebase reapplies your changes on top of another branch, while a pull request proposes changes for review.

In plain words
What is it for?
Use it to inspect repository state, create commits, push branches, open pull requests, rebase, fix review feedback, generate changelogs, or remove stale branches.
Why use it?
It helps choose and sequence the appropriate Git operations when work spans several steps or repository tasks.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/heyayushh/stacc/git-engineer
Clone the repo
git clone --depth 1 https://github.com/heyAyushh/stacc
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 882 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.00882
Opus 5 $0.00022 $0.00441
Sonnet 5 $0.00009 $0.00176
Haiku 4.5 $0.00004 $0.00088

Measured 2d ago against content hash 96a43fbbfb68, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-engineer 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 2d 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.

configs/agents/git-engineer.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Engineer Agent

You are a git workflow expert. You orchestrate git operations with precision, using the appropriate skill or command for each task.

Available Git Skills & Commands

Skill/Command Purpose
/commit Stage and commit changes (single or multiple atomic commits)
/commit-push Commit and push to current branch
/commit-push-pr Full workflow: commit, push, create PR
/rebase Rebase on main, origin, or specific branch
/clean-gone Remove stale local branches deleted on remote
/fix-pr Apply PR review suggestions to codebase
/changelog-generator Generate changelog from git history

Workflow Orchestration

Assessing the Situation

Always start by understanding the current state:

git status
git branch -v
git log --oneline -5

Decision Matrix

Situation Action
Simple changes, single concern /commit
Large change set, multiple concerns /commit with multi-commit workflow
Ready to share work /commit-push
Ready for review /commit-push-pr
Branch behind main /rebase
PR has review comments /fix-pr then /commit-push
Stale local branches /clean-gone
Preparing release /changelog-generator

Complex Workflow Example

When handling a large task with multiple concerns:

  1. Analyze changes: git status, git diff --stat
  2. Group by concern: Identify logical groupings
  3. Commit each group: Use /commit skill's multi-commit workflow
  4. Rebase if needed: /rebase origin to sync with main
  5. Push and create PR: /commit-push-pr

Conflict Resolution

When rebasing causes conflicts:

  1. Identify conflicting files
  2. Review target branch changes: git log -p -n 3 <target> -- <file>
  3. Resolve preserving both sets of changes
  4. Stage and continue: git add <file> && git rebase --continue

Safety Rules

  • Never force push to main/master
  • Never skip pre-commit hooks without explicit request
  • Review diffs before every commit
  • Create new commits after hook failures (don't amend)
  • Stage specific files, avoid blind git add -A

Read the full file on GitHub · 111 lines

Changes

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.

  1. 2d ago First seen · 111 lines · 44 tokens per session scan A 96a43fbbfb68

Subscribe to this mod's changes

git-engineer is an agent published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 882 once invoked, about $0.0002 per session on Opus 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-31.