git-workflow

A Git workflow rule set covering status checks, Conventional Commits, and pushing changes from MSYS2 bash, a Unix-like shell for Windows.

In plain words
What is it for?
It is for checking changes, preparing commits with summaries and verification notes, and pushing Rust project updates.
Why use it?
It makes the required order and commit details explicit and helps catch formatting problems before code is pushed.

Cursor rule for Cursor

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 rules/platinoff/poolai/git-workflow
Clone the repo
git clone --depth 1 https://github.com/platinoff/poolAI

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,352 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.00000 $0.01352
Opus 5 $0.00000 $0.00676
Sonnet 5 $0.00000 $0.00270
Haiku 4.5 $0.00000 $0.00135

Measured yesterday against content hash f6231994e2d9, 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.

.cursor/rules/git-workflow.mdc · 96 lines

How it starts

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

Git Workflow — Conventional Commits (CL) & Push

⚠️ CRITICAL: MSYS2 bash only

All git commands run in MSYS2 bash (C:\msys64\usr\bin\bash.exe).
Do NOT use PowerShell, cmd, or Cursor integrated terminal for git (CreateFileMapping, index.lock, truncated output). Use external MSYS2 UCRT64 only.

Git order (status → commit → push)

  1. git status --short — check modified/unstaged first.
  2. Read/modify files before git add if needed (AI: avoid staging files you still need to edit).
  3. git add <paths> or git add -A (use with care).
  4. git commitCL (Conventional Commits) subject + Summary у тілі, якщо в коміті є код (див. нижче).
  5. git push — pre-push hook runs cargo fmt --all --check; fix format then re-commit if it fails.

Summary у коміті (якщо є зміни коду)

Перед git commit перевір staged diff (git diff --cached --stat).

  • Є зміни в src/, tests/, crates/, Cargo.toml → commit з обов’язковим тілом Summary: (кілька -m або HEREDOC): що змінено, які cargo команди прогнані, FM/scope за наявності.
  • Лише docs/, .cursor/, README без коду → subject + короткий Summary (рекомендовано).
  • Шаблон і приклад — .cursor/commands/git-push.md п.3a; після push — самарі в чат п.3b.

Commit format (CL = Conventional Commits)

<type>(<scope>): <subject>

[optional body - рекомендується: 2-4 bullet points]

[optional footer]

Types: feat | fix | docs | style | refactor | perf | test | build | ci | chore | revert
Scope examples: vm, ui, raid, network, cloud, ml, docs, scripts, concept
Subject: imperative, lowercase, ~50 chars.

Commit summary/body (2–4 bullets)обов’язково, якщо коміт містить код (див. вище):

  • що саме зроблено (модулі, FM-id)
  • які перевірки виконані (cargo fmt, cargo test-ci, clippy — що реально запускали)
  • нотатки (features, env, не стаджити data/audit/*.log.gz)

Read the full file on GitHub · 96 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. yesterday First seen · 96 lines · 0 tokens per session scan A f6231994e2d9

Subscribe to this mod's changes

git-workflow is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,352 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-31.