Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/GuillemRoca/agent-skills-androidnpx agentmods add skills/guillemroca/agent-skills-android/git-workflow-and-versioningWrote 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/skills/guillemroca/agent-skills-android/git-workflow-and-versioning)<a href="https://agentmods.dev/skills/guillemroca/agent-skills-android/git-workflow-and-versioning"><img src="https://agentmods.dev/badge/skills/guillemroca/agent-skills-android/git-workflow-and-versioning.svg" alt="Measured on agentmods" 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.00041 | $0.01788 |
| Opus 5 | $0.00020 | $0.00894 |
| Sonnet 5 | $0.00008 | $0.00358 |
| Haiku 4.5 | $0.00004 | $0.00179 |
Grade A, and why
git-workflow-and-versioning 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 7d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow and Versioning
Overview
Trunk-based development: keep main always deployable, use short-lived feature branches (1–3 days), and make atomic commits that address one logical concern. Android versioning requires managing versionCode (monotonic integer for Play Store) and versionName (human-readable semver).
When to Use
- Starting a new feature branch
- Making commits during development
- Preparing a release
- Managing version numbers
- Reviewing branch strategy or merge approach
- Setting up signing configurations
Skip when: The project has an established, documented git workflow.
Core Process
Step 1: Trunk-Based Development
- Branch strategy:
main (always deployable)
├── feature/task-sharing (1-3 days, then merge)
├── feature/dark-mode (1-3 days, then merge)
├── fix/crash-on-empty-list (hours, then merge)
└── release/1.2.0 (cut from main, hotfixes only)
- Branch rules:
mainis always green (CI passes)- Feature branches are short-lived (1–3 days max)
- Delete branches after merge
- No long-lived feature branches — use feature flags instead
- Release branches are cut from
main, not from feature branches
Step 2: Atomic Commits
- Each commit addresses one logical concern:
# GOOD: atomic commits
git commit -m "$(cat <<'EOF'
Add TaskDao with CRUD operations
Room DAO for tasks table with observe, upsert, and delete operations.
Flow-based observation for reactive UI updates.
EOF
)"
git commit -m "$(cat <<'EOF'
Add TaskRepository with offline-first sync
Implements TaskRepository interface. Local Room database is the source
of truth. Remote sync via Retrofit with error handling for network
failures.
EOF
)"
# BAD: kitchen sink commit
git commit -m "Add task feature with database, API, UI, and tests"
- Commit message format:
- First line: imperative, under 72 characters ("Add", "Fix", "Update", "Remove")
- Blank line
- Body: explain why, not what (the diff shows what)
- Reference issue numbers:
Fixes #42
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.
- 7d ago First seen · 253 lines · 41 tokens per session scan A 101a88a36b43
git-workflow-and-versioning is a skill published in the GitHub repository GuillemRoca/agent-skills-android (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,788 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
github-operations
WORKFLOW SKILL — Full GitHub contribution lifecycle: branches, conventional commits, issues, PRs, Actions, releases. gh CLI-first with MCP fallback. WHEN: "commit", "push", "open PR", "create branch", "create issue", "cut release", "GitHub operation". DO NOT USE FOR: Azure infrastructure, Bicep/Terraform code…