Borrowing it
Nothing to install: this file belongs to ProvarTesting/provardx-cli. 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/ProvarTesting/provardx-cli/main/.claude/commands/git-workflow.mdgit clone --depth 1 https://github.com/ProvarTesting/provardx-cliWrote 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/commands/provartesting/provardx-cli/git-workflow)<a href="https://agentmods.dev/commands/provartesting/provardx-cli/git-workflow"><img src="https://agentmods.dev/badge/commands/provartesting/provardx-cli/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/commands/provartesting/provardx-cli/git-workflow"><img src="https://agentmods.dev/badge/commands/provartesting/provardx-cli/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.01954 |
| Opus 5.5 | $0.00000 | $0.00782 |
| Sonnet 5.5 | $0.00000 | $0.00391 |
| Haiku 4.5 | $0.00000 | $0.00195 |
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 2mo 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are executing the provardx-cli development git workflow. Follow these steps in order. Stop and confirm with the user at each CONFIRM point before proceeding.
Step 0 — Establish the Jira ticket (planning phase)
Ask the user:
"Do you have a PDX ticket for this work? A) Yes — give me the number B) No — create one now as part of planning C) No ticket needed (framework/chore work)"
Option A — Existing ticket
User provides the ticket number. Set TICKET = PDX-<number>.
Fetch the ticket to confirm it exists and read its summary and status:
- Call
getAccessibleAtlassianResourcesto get the cloudId for your Jira instance, then usegetJiraIssue(cloudId:<from above>, issueIdOrKey:PDX-<number>) - Show the user: ticket summary, current status, and URL
- If the ticket is already Closed, warn the user before proceeding
Skip to Derive branch variables below.
Option B — Create ticket now (planning phase)
Ask the user a single compound question to gather everything at once:
"Tell me about the work — I'll draft the ticket from your answer:
- What should this change do? (one sentence — becomes the ticket summary)
- Is it a new feature, bug fix, infrastructure/CI work, research spike, or internal task?
- Why is it needed? What problem or requirement drives it?
- How will we know it's done? (acceptance criteria — list conditions)
- Anything explicitly out of scope?"
From the user's answer, draft the full ticket content. Use your judgment to infer issue type if the user is vague. Do not ask follow-up questions unless a critical field (summary or acceptance criteria) is completely missing.
Issue type mapping:
| Work described | Issue type |
|---|---|
| New user-facing capability | Story |
| Something broken | Bug |
| CI, infra, tooling, architecture | Enabler |
| Research / investigation / prototype | Spike |
| Internal work, no user impact | Task |
CONFIRM: Show the drafted ticket for review before creating:
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.
- 2mo ago First seen · 256 lines · 0 tokens per session scan A 14fce5618ba6
git-workflow is a command published in the GitHub repository ProvarTesting/provardx-cli (1 stars, last pushed 3mo ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 1,954 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.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
codex-review
Use when asked to check, turn on, turn off, or switch this repo's Codex review mode (local, github, or off), or to report the effective mode and Codex sandbox status.
test-audit
Writes a versioned TESTAUDIT.md; with --fix, quarantines the rot in gated, revertible commits. TRIGGER WHEN: auditing a test suite, measuring test health, finding dead or flaky or redundant tests, or diagnosing failure causes and proposing temporary quarantine. DO NOT TRIGGER WHEN: one module's tests are consolidated…