Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
A skill your agent uses for any git work such as creating branches, staging changes, writing commit messages, pushing branches, or preparing pull requests.
Install Git Workflow
$ npx skills add fmflurry/settings-opencode --skill git-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fmflurry/settings-opencode git-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/fmflurry/settings-opencode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/git-workflow .claude/skills/git-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "git-workflow" agent skill from https://github.com/fmflurry/settings-opencode/tree/master/skills/git-workflow into .claude/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/fmflurry/settings-opencode/tree/master/skills/git-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add fmflurry/settings-opencode --skill git-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fmflurry/settings-opencode git-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fmflurry/settings-opencode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/git-workflow .agents/skills/git-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "git-workflow" agent skill from https://github.com/fmflurry/settings-opencode/tree/master/skills/git-workflow into .agents/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fmflurry/settings-opencode --skill git-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fmflurry/settings-opencode git-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fmflurry/settings-opencode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/git-workflow .cursor/skills/git-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "git-workflow" agent skill from https://github.com/fmflurry/settings-opencode/tree/master/skills/git-workflow into .cursor/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/fmflurry/settings-opencode.git --path skills/git-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add fmflurry/settings-opencode --skill git-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fmflurry/settings-opencode git-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fmflurry/settings-opencode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/git-workflow .gemini/skills/git-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "git-workflow" agent skill from https://github.com/fmflurry/settings-opencode/tree/master/skills/git-workflow into .gemini/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install fmflurry/settings-opencode git-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add fmflurry/settings-opencode --skill git-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/fmflurry/settings-opencode.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/git-workflow .github/skills/git-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "git-workflow" agent skill from https://github.com/fmflurry/settings-opencode/tree/master/skills/git-workflow into .github/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fmflurry/settings-opencode --skill git-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install fmflurry/settings-opencode git-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fmflurry/settings-opencode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/git-workflow .opencode/skills/git-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "git-workflow" agent skill from https://github.com/fmflurry/settings-opencode/tree/master/skills/git-workflow into .opencode/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
git-workflow- GitHub stars
- 171
- Token cost
- ~1.1k tokens
- SKILL.md length
- 584 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses for any git work such as creating branches, staging changes, writing commit messages, pushing branches, or preparing pull requests.
- Any git work such as creating branches
- SKILL.md covers When to Activate, Required Delegation, Commit Convention and Branch Convention, plus 3 more sections
- Calls az and git
- Staging changes
What it does
Git Workflow is an agent skill from fmflurry/settings-opencode. Use this skill for any git work such as creating branches, staging changes, writing commit messages, pushing branches, or preparing pull requests. Delegates git execution to the git-specialist agent.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Git workflow, Commit messages and Pull requests. It works with Git. The repository describes itself as: Custom OpenCode settings. The licence is MIT.
When your agent uses it
- Any git work such as creating branches
- Staging changes
- Writing commit messages
- Pushing branches
Example prompts
- “/git-workflow”
What it can do on your machine
Read from SKILL.md and the folder at commit 0e6c33c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
azgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use az and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Git Workflow loads about 1.1k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 584 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from fmflurry/settings-opencode at commit 0e6c33c, republished under its MIT licence (© fmflurry). 584 words, ~1,125 tokens.
Download SKILL.mdSave it as
.claude/skills/git-workflow/SKILL.md (or your agent's skills folder).- name
- git-workflow
- description
- Use this skill for any git work such as creating branches, staging changes, writing commit messages, pushing branches, or preparing pull requests. Delegates git execution to the git-specialist agent.
Git Workflow Skill
Use this skill whenever the task involves git.
When to Activate
- Creating or renaming branches
- Staging changes
- Writing commit messages
- Creating commits
- Pushing branches
- Preparing pull requests
- Reviewing branch names or commit message format
Required Delegation
When git work is needed, delegate to the dedicated git-specialist subagent via the /git command.
- Do not handle substantive git workflow directly in the main agent when
/gitcan handle it. - Use the
git-specialistagent for branch naming, commit message drafting, staging, commits, and pushes. - Keep non-git implementation work in the main agent, then switch to
/gitfor repository operations. - If you are already the
git-specialistagent, execute the git task directly and do not re-delegate it.
Commit Convention
Every commit message must follow this format:
<type>(<scope>): <short summary>
[optional body]
[optional footer(s)]When scope is not useful or not clear, this no-scope form is also valid:
<type>: <short summary>Allowed Types
feat: A new featurefix: A bug fixdocs: Documentation only changesstyle: Changes that do not affect behavior, such as formattingrefactor: Code changes that neither fix a bug nor add a featuretest: Adding or correcting testschore: Maintenance tasks such as tooling or build updates
Commit Rules
- English only: subject and body MUST be English, even when the diff or conversation is French.
- Prefer including a meaningful
scopewhen the affected area is clear - Omit
scopeinstead of inventing one when it is not clear - Use a concise present-tense summary
- Keep the summary focused on intent, not a file-by-file changelog
- Match the type to the actual purpose of the change
Examples
feat(api): add user authentication endpointfix(auth): prevent empty login submissionchore(settings): sync opencode configuration
Branch Convention
Every branch name must follow this format:
<type>/<scope>-<short-description>Branch Rules
- Reuse the same allowed
typevalues as commits scopeis required for branchesscopemust be a single lowercase token with letters and numbers only- The first
-after/separatesscopefromshort-description - Use a short kebab-case description
- Keep the branch name specific to the actual change
- If branch scope is ambiguous, ask one short question before creating the branch
Examples
feat/auth-login-formfix/api-token-refreshchore/settings-git-workflow
Show full SKILL.md (241 more words)Show less
Git Specialist Expectations
The git-specialist agent must:
- inspect repository status before acting
- draft compliant branch names and commit messages
- stage only relevant changes
- avoid destructive git commands unless explicitly requested
- push only when requested or clearly part of the delegated git task
- detect the host from
git remote get-url originand use the matching CLI for PR work:ghfor GitHub,az repos prfor Azure DevOps - preserve repository history hygiene
Pull Request Rules
When the task includes PR creation or inspection:
- detect the host from
git remote get-url origin:github.com→ useghdev.azure.com/visualstudio.com→ useaz repos pr(Azure CLI +azure-devopsextension)- otherwise → stop and report an unsupported host
- push the current branch with upstream tracking first if needed
- if a PR already exists for the current branch, return that URL instead of creating a duplicate
- choose the base branch from the repository default branch when available, otherwise prefer
main, thenmaster - use a concise PR title aligned with the branch purpose and commit intent (conventional commit format)
- include a short
## Summarysection in the PR body - Azure DevOps defaults: reviewers = group
PIXELS;--draftis not supported byaz repos pr(ignore the flag for Azure)
Output Expectations
For git tasks, return:
- the branch name used or proposed
- the commit message used or proposed
- whether the branch was pushed
- the pull request URL when a PR exists or was created
- any blockers, such as ambiguous scope or unstaged unrelated changes
© fmflurry, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/git-workflow of fmflurry/settings-opencode.
Open the folder on GitHubat commit 0e6c33c
Compare with similar skills
Git Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Git Workflow this skillfmflurry/settings-opencode | 171 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 103k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Emoji Commit ConventionsbaptisteArno/typebot.io | 11k | — | ~424 | Automated safety check: Pass | Custom licence | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 | |
| Adk Gitgoogle/adk-python | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
- Official
Adk Git
google/adk-python
Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and…
Git PR Flow
wgzhao/Addax
Standard branch, commit, and pull-request workflow for this repo.
More from fmflurry/settings-opencode
All 20 skills in this repoShow Your Work
fmflurry/settings-opencode
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result).
Playwright E2E Authoring
fmflurry/settings-opencode
Scaffold and extend Playwright E2E tests for the gc.platform suite (tests/playwright), wiring every artifact to the real frontend (localhost:4200) + real .NET backend — never mocks.
Why
fmflurry/settings-opencode
A skill your agent uses for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.
Angular Accessibility
fmflurry/settings-opencode
Audit and fix common accessibility issues in Angular templates and Angular Material components.
Angular Clean Architecture
fmflurry/settings-opencode
Scaffolds and extends Angular standalone feature MODULES under src/app/modules/{name} using Clean Architecture layering (presentation/application/core/infrastructure), a self-registering module…
Angular Cop
fmflurry/settings-opencode
Pre-merge code review for Angular + TypeScript pull requests.
Related
Works with
Categories
Questions about Git Workflow
What does Git Workflow do?
A skill your agent uses for any git work such as creating branches, staging changes, writing commit messages, pushing branches, or preparing pull requests. Git Workflow is an agent skill from fmflurry/settings-opencode. Use this skill for any git work such as creating branches, staging changes, writing commit messages, pushing branches, or preparing pull requests.
When should I use Git Workflow?
Git Workflow fits situations like: any git work such as creating branches; staging changes; writing commit messages; pushing branches.
How do I install Git Workflow in Claude Code?
Run `npx skills add fmflurry/settings-opencode --skill git-workflow -a claude-code`. Or copy the skill folder (skills/git-workflow in fmflurry/settings-opencode) into .claude/skills/git-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Git Workflow in Codex?
Run `npx skills add fmflurry/settings-opencode --skill git-workflow -a codex`. Or copy the skill folder (skills/git-workflow in fmflurry/settings-opencode) into .agents/skills/git-workflow in your project. Codex loads it when a task matches its description.
Can I use Git Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fmflurry/settings-opencode --skill git-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-workflow, .gemini/skills/git-workflow, .github/skills/git-workflow and .opencode/skills/git-workflow in your project.
What does Git Workflow need to run?
Going by SKILL.md and its folder, Git Workflow needs the command-line tools its instructions call (az and git).
Does Git Workflow access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Git Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Git Workflow use?
Git Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Git Workflow use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Git Workflow?
Skills that share tags, products or a category with Git Workflow: Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars) and Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Git Workflow?
fmflurry (a GitHub user) maintains it in fmflurry/settings-opencode, which has 171 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 7, 2026.
Source: fmflurry/settings-opencode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.