What is atlassian-mcp-server git-workflow.md?

A set of rules for using Git and GitHub, the tools that store code history and host code collaboration, in an Atlassian MCP server project.

Use it to create branches, make structured commits, push changes, and follow the project's pull-request process.

It standardizes branches, commit messages, and pull requests so changes are traceable and are not made directly on the main branch.

How InfraMCP/atlassian-mcp-server configures Kiro

Reuse

Borrowing it

Nothing to install: this file belongs to InfraMCP/atlassian-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/InfraMCP/atlassian-mcp-server/main/.kiro/steering/git-workflow.md

Clone the repo

git clone --depth 1 https://github.com/InfraMCP/atlassian-mcp-server

Made for: Kiro.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/inframcp/atlassian-mcp-server/git-workflow/github.svg)](https://agentmods.dev/instructions/inframcp/atlassian-mcp-server/git-workflow)

Your own site

<a href="https://agentmods.dev/instructions/inframcp/atlassian-mcp-server/git-workflow"><img src="https://agentmods.dev/badge/instructions/inframcp/atlassian-mcp-server/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/inframcp/atlassian-mcp-server/git-workflow"><img src="https://agentmods.dev/badge/instructions/inframcp/atlassian-mcp-server/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 722 This file is loaded in full into every session.

When invoked 722 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00722	$0.00722
Opus 5.5	$0.00289	$0.00289
Sonnet 5.5	$0.00144	$0.00144
Haiku 4.5	$0.00072	$0.00072

Measured 15d ago against content hash 8ae22b730f21, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

atlassian-mcp-server git-workflow.md 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 15d 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.

.kiro/steering/git-workflow.md · 101 lines

How it starts

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

Git & GitHub Workflow

Automation Philosophy

Full automation required - Use GitHub MCP tools for all operations. Never ask user to manually create branches, commits, or PRs.

Branch Naming

Format: <type>/<short-description> (kebab-case, 3-5 words max)

feature/ - New features
fix/ or bugfix/ - Bug fixes
hotfix/ - Critical fixes
chore/ - Maintenance tasks
docs/ - Documentation updates

Always branch from main, never commit directly to it.

Commit Messages

Format: <type>(<scope>): <subject>\n\n<body>\n\n<footer>

Types: feat, fix, docs, style, refactor, perf, test, chore, ci

Rules:

Subject: ≤50 chars, imperative mood ("add" not "added")
Body: Explain what and why, wrap at 72 chars
Footer: Reference issues ("Closes #123", "Fixes #123")
Be specific, avoid vague messages

Example:

feat(confluence): add label management tools

Add tools for getting, searching, and managing page labels including
confluence_get_page_labels and confluence_search_by_label methods.

Closes #42

Pull Request Workflow

Automated steps:

Create branch: mcp_github_create_branch
Push changes: mcp_github_push_files (with commit message)
Create PR: mcp_github_create_pull_request (with description)

PR Title: Same format as commit messages (e.g., feat(confluence): add label tools)

PR Description:

## Description
[What this PR does]

## Changes Made
- [Change 1]
- [Change 2]

## Type of Change
- [ ] Bug fix / [ ] New feature / [ ] Breaking change / [ ] Documentation

## Related Issues
Closes #[number]

Keep PRs focused (one feature/fix), small (<500 lines), and always link issues.

GitHub MCP Tools

Primary tools:

mcp_github_create_branch - Create branches
mcp_github_push_files - Push commits
mcp_github_create_pull_request - Create PRs
mcp_github_get_file_contents - Check file state
mcp_github_create_issue / mcp_github_update_issue - Issue management

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

15d ago First seen · 101 lines · 722 tokens per session scan A 8ae22b730f21

Subscribe to this mod's changes

atlassian-mcp-server git-workflow.md is an instructions file published in the GitHub repository InfraMCP/atlassian-mcp-server (4 stars, last pushed 15d ago), licensed MIT. It adds 722 tokens to every session, about $0.0029 per session on Opus 5.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-10-22.

Commits Git and workflow

atlassian-mcp-server git-workflow.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
atlassian-mcp-server git-workflow.mdInfraMCP/atlassian-mcp-server	Instructions file	4	15d ago	MIT	A	722	Kiro
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

atlassian-mcp-server: Instructions file for Kiro