What is git-workflow?

A set of rules for handling Git work, software releases, and pull-request drafts in a code repository. It keeps the agent from changing Git history and leaves commits and publishing to a person.

Use it when reviewing changes, preparing a release, or drafting a pull request. It helps inspect differences, follow Conventional Commits such as `fix:` or `feat:`, and maintain an uncommitted `PR.txt` file.

It prevents an agent from accidentally staging files, creating commits, merging branches, or pushing changes. It also keeps the pull-request summary and test notes aligned with the current branch.

git-workflow — Agent by callstack

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/callstack/react-native-testing-library/git-workflow

Clone the repo

git clone --depth 1 https://github.com/callstack/react-native-testing-library

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 276 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00276
Opus 5	$0.00000	$0.00138
Sonnet 5	$0.00000	$0.00055
Haiku 4.5	$0.00000	$0.00028

Measured yesterday against content hash eec5b8ab5ae5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

agents/git-workflow.md · 21 lines

What it actually says

Git, Releases, And PR Workflow

Agent git restrictions

Never run git commands that create commits, push, or modify the index/history. The human owns these actions.
Forbidden commands include (non-exhaustive): git commit, git push, git add, git rm, git restore --staged, git reset, git rebase, git merge, git cherry-pick, git stash, git commit --amend, and git tag.
Read-only inspection is fine: git status, git log, git diff, git show, git blame.
When conflicts or staging are involved, resolve file contents in the working tree only, then hand off to the human to stage and commit. Describe the exact commands you would run instead of running them.

Commits and releases

Use Conventional Commits such as fix:, feat:, and chore:.
Releases are managed with release-it.

PR draft workflow

Maintain PR.txt at the repository root using the structure from .github/pull_request_template.md.
Keep PR.txt aligned with the current branch diff relative to origin/main.
Include tests actually run and any known validation gaps in PR.txt.
Do not commit PR.txt.

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.

yesterday First seen · 21 lines · 0 tokens per session scan A eec5b8ab5ae5

Subscribe to this mod's changes

git-workflow is an agent published in the GitHub repository callstack/react-native-testing-library (3,414 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 276 tokens. 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.

Code review Git and workflow ReAct Testing jest react-native

code-architect-reviewer

Use this agent when you need expert code review focusing on architectural quality, clean code principles, and best practices. Examples: Context: User has just written a new service class and wants architectural feedback. user: 'I just implemented a user authentication service. Can you review it?' assistant: 'I'll use…

lingodotdev/lingo.dev · 0 tokens

business-analyst

Business Analyst. Domain understanding, ubiquitous language, business rules, and bounded contexts; bridge collaboration, not message ferrying. Triggers: domain analysis, business rules, ubiquitous language, bounded context, Analysis Patterns, Business Analysis.

felixzhu97/explore-chat · 0 tokens

customer

End user (Customer). Product feedback and improvement suggestions from a user perspective. Triggers: user feedback, customer perspective, experience critique, improvement ideas, usability. Use proactively when reviewing UI flows or after feature demos.