What is git-workflow?

A guided Git workflow for Provar DX CLI development. Git is a tool for tracking code changes, while Jira is a system for managing work tickets.

Use it to establish or create a Jira ticket, verify its status, derive branch details, and follow the project’s Git process.

It keeps planning, ticket checks, branch setup, and later development steps in order, with confirmation points before continuing.

git-workflow — Command by ProvarTesting

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 commands/provartesting/provardx-cli/git-workflow

Clone the repo

git clone --depth 1 https://github.com/ProvarTesting/provardx-cli

Made for: Claude Code.

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 1,954 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.01954
Opus 5	$0.00000	$0.00977
Sonnet 5	$0.00000	$0.00391
Haiku 4.5	$0.00000	$0.00195

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

.claude/commands/git-workflow.md · 256 lines

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 getAccessibleAtlassianResources to get the cloudId for your Jira instance, then use getJiraIssue (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:

Read the full file on GitHub · 256 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.

yesterday First seen · 256 lines · 0 tokens per session scan A 14fce5618ba6

Subscribe to this mod's changes

git-workflow is a command published in the GitHub repository ProvarTesting/provardx-cli (1 stars, last pushed 1mo 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.

Git and workflow Productivity Testing provar provardx quality salesforce

git-workflow

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Step 0 — Establish the Jira ticket (planning phase)

Option A — Existing ticket

Option B — Create ticket now (planning phase)

What this file has done since we first saw it

Other commands, from other repositories

activity

review

test

judge

against

compare