Agent skill

Managing Git

by CloudAI-X in CloudAI-X/opencode-workflow

Guides git workflows, branching strategies, commit conventions, and version control best practices.

MITAuto-check passedDevelopment

Install Managing Git

skills CLI

$ npx skills add CloudAI-X/opencode-workflow --skill managing-git -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install CloudAI-X/opencode-workflow managing-git --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/opencode-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/managing-git .claude/skills/managing-git && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "managing-git" agent skill from https://github.com/CloudAI-X/opencode-workflow/tree/main/skills/managing-git into .claude/skills/managing-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-git", 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

$skill-installer install https://github.com/CloudAI-X/opencode-workflow/tree/main/skills/managing-git

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

skills CLI

$ npx skills add CloudAI-X/opencode-workflow --skill managing-git -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install CloudAI-X/opencode-workflow managing-git --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/opencode-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/managing-git .agents/skills/managing-git && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "managing-git" agent skill from https://github.com/CloudAI-X/opencode-workflow/tree/main/skills/managing-git into .agents/skills/managing-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-git", 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.

skills CLI

$ npx skills add CloudAI-X/opencode-workflow --skill managing-git -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install CloudAI-X/opencode-workflow managing-git --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/opencode-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/managing-git .cursor/skills/managing-git && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "managing-git" agent skill from https://github.com/CloudAI-X/opencode-workflow/tree/main/skills/managing-git into .cursor/skills/managing-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-git", 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

$ gemini skills install https://github.com/CloudAI-X/opencode-workflow.git --path skills/managing-git

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add CloudAI-X/opencode-workflow --skill managing-git -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install CloudAI-X/opencode-workflow managing-git --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/opencode-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/managing-git .gemini/skills/managing-git && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "managing-git" agent skill from https://github.com/CloudAI-X/opencode-workflow/tree/main/skills/managing-git into .gemini/skills/managing-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-git", 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.

GitHub CLI

$ gh skill install CloudAI-X/opencode-workflow managing-git

Installs 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).

skills CLI

$ npx skills add CloudAI-X/opencode-workflow --skill managing-git -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/opencode-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/managing-git .github/skills/managing-git && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "managing-git" agent skill from https://github.com/CloudAI-X/opencode-workflow/tree/main/skills/managing-git into .github/skills/managing-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-git", 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.

skills CLI

$ npx skills add CloudAI-X/opencode-workflow --skill managing-git -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install CloudAI-X/opencode-workflow managing-git --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/opencode-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/managing-git .opencode/skills/managing-git && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "managing-git" agent skill from https://github.com/CloudAI-X/opencode-workflow/tree/main/skills/managing-git into .opencode/skills/managing-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-git", 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: managing-git
GitHub stars: 275
Token cost: ~2.5k tokens
SKILL.md length: 543 words
Files: 1
Skills in repo: 7
Repo updated: Jan 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Guides git workflows, branching strategies, commit conventions, and version control best practices.

Works in 4 steps: Lowercase with hyphens → Include ticket number when available → Keep short but descriptive → …
Managing repositories
SKILL.md covers When to Use This Skill, Branching Strategies, Commit Message Conventions and Branch Naming Conventions, plus 4 more sections
Calls git and npm

What it does

Managing Git is an agent skill from CloudAI-X/opencode-workflow. Guides git workflows, branching strategies, commit conventions, and version control best practices. Use when managing repositories, creating branches, or handling merges.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: opencode

It sits in Development, covering Git workflow and Commit messages. It works with Git. The licence is MIT.

When your agent uses it

Managing repositories
Creating branches
Handling merges

Example prompts

“Use the managing-git skill to guide git workflows, branching strategies, commit conventions, and version control best practices”
“/managing-git”

Requirements

Node.js
Compatibility (from SKILL.md): opencode

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Lowercase with hyphens
Include ticket number when available
Keep short but descriptive
Delete after merge

What it can do on your machine

Read from SKILL.md and the folder at commit 0128ca6. 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:
- git
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and npm, 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.
Compatibility
opencode
From compatibility in the SKILL.md frontmatter.

Context cost

Managing Git loads about 2.5k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 543 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~46
When it runs · the whole SKILL.md, loaded when a task matches: ~2.5k

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 CloudAI-X/opencode-workflow at commit 0128ca6, republished under its MIT licence (© CloudAI-X). 543 words, ~2,496 tokens.

Download SKILL.mdSave it as .claude/skills/managing-git/SKILL.md (or your agent's skills folder).

name: managing-git
description: Guides git workflows, branching strategies, commit conventions, and version control best practices. Use when managing repositories, creating branches, or handling merges.
compatibility: opencode
license: MIT
metadata.category: workflow
metadata.audience: developers

Managing Git

Best practices for version control, branching strategies, and collaborative development.

When to Use This Skill

Setting up branching strategies
Writing commit messages
Handling merges and conflicts
Managing releases
Code review workflows
Maintaining clean history

Branching Strategies

Git Flow

main ─────●─────────────────────●─────────────────●────▶
           \                   /                 /
release     \───────●─────────●                 /
              \                                /
develop ───────●───────●───────●──────●───────●────────▶
                \       \       \      \
feature          \───────●───────●      \───●───●
                          \              \
hotfix                     \              \───●────▶ main

Branch	Purpose	Branches From	Merges Into
`main`	Production code	-	-
`develop`	Integration	main	release
`feature/*`	New features	develop	develop
`release/*`	Release prep	develop	main, develop
`hotfix/*`	Production fixes	main	main, develop

Use when: Scheduled releases, multiple versions supported

GitHub Flow

main ─────●─────●─────●─────●─────●────▶
           \   /       \   /       \   /
feature     ●─●         ●─●         ●─●
            PR          PR          PR

Branch	Purpose
`main`	Always deployable
`feature/*`	All changes (features, fixes)

Use when: Continuous deployment, simple workflow

Trunk-Based Development

main ─────●──●──●──●──●──●──●──●──●──●────▶
           │  │  │  │  │  │  │  │  │  │
          ●   ●  ●  ●  ●  ●  ●  ●  ●  ●
          Small, frequent commits (often direct to main)

Use when: High trust teams, strong CI/CD, frequent deploys

Commit Message Conventions

Conventional Commits

<type>(<scope>): <subject>

<body>

<footer>

Types

Type	Description	Example
`feat`	New feature	`feat(auth): add OAuth2 login`
`fix`	Bug fix	`fix(api): handle null response`
`docs`	Documentation	`docs(readme): update setup steps`
`style`	Formatting	`style: fix indentation`
`refactor`	Code restructuring	`refactor(db): simplify query builder`
`test`	Adding tests	`test(user): add registration tests`
`chore`	Maintenance	`chore(deps): update lodash`
`perf`	Performance	`perf(search): add index on email`
`ci`	CI/CD changes	`ci: add Node 18 to matrix`

Good vs Bad Commits

BAD:
  - "fix"
  - "update code"
  - "WIP"
  - "changes"
  - "asdfasdf"

GOOD:
  - "fix(auth): prevent session timeout on idle"
  - "feat(cart): add quantity validation"
  - "refactor(api): extract common error handling"

Commit Body Guidelines

fix(payment): prevent double charge on retry

The payment gateway timeout was causing the retry logic to submit
duplicate charges. Added idempotency key to prevent double-processing.

Closes #1234

First line: 50 chars max, imperative mood
Body: Wrap at 72 chars, explain why, not what
Footer: Reference issues, breaking changes

Branch Naming Conventions

Pattern

<type>/<ticket>-<short-description>

Examples

Type	Example
Feature	`feature/AUTH-123-add-oauth-login`
Bugfix	`fix/CART-456-quantity-validation`
Hotfix	`hotfix/PROD-789-memory-leak`
Chore	`chore/update-dependencies`
Docs	`docs/api-documentation`

Branch Rules

Lowercase with hyphens
Include ticket number when available
Keep short but descriptive
Delete after merge

Git Workflow Commands

Daily Workflow

bash

# Start new feature
git checkout main
git pull origin main
git checkout -b feature/AUTH-123-add-login

# Work on feature
git add -p                    # Stage hunks interactively
git commit -m "feat(auth): add login form"

# Keep up to date
git fetch origin
git rebase origin/main        # Preferred: clean history
# OR
git merge origin/main         # Alternative: preserves context

# Push and create PR
git push -u origin feature/AUTH-123-add-login

Useful Commands

Command	Purpose
`git stash`	Save uncommitted changes temporarily
`git stash pop`	Restore stashed changes
`git commit --amend`	Modify last commit
`git rebase -i HEAD~3`	Interactive rebase (squash, reorder)
`git cherry-pick <sha>`	Apply specific commit
`git bisect`	Binary search for bug introduction
`git reflog`	View all HEAD movements (recovery)

Cleanup Commands

bash

# Delete merged branches locally
git branch --merged | grep -v main | xargs git branch -d

# Prune remote tracking branches
git fetch --prune

# Clean untracked files (careful!)
git clean -fd

Handling Conflicts

Conflict Resolution Flow

1. Identify conflicts
   git status

2. Open conflicted files
   <<<<<<< HEAD
   your changes
   =======
   their changes
   >>>>>>> feature-branch

3. Resolve (keep one, combine, or rewrite)

4. Mark resolved
   git add <resolved-file>

5. Continue
   git rebase --continue   # if rebasing
   git commit              # if merging

Prevention Strategies

Small, frequent merges - Reduce conflict scope
Communication - Coordinate on shared files
Feature flags - Reduce long-lived branches
Clear ownership - Minimize overlapping work

Show full SKILL.md (213 more words)Show less

Pull Request Best Practices

PR Checklist

Branch is up to date with main
Tests pass locally
Linting passes
Self-review completed
Documentation updated
Ticket/issue linked
Screenshots for UI changes

PR Size Guidelines

Size	Lines Changed	Review Time	Recommendation
Small	1-100	15 min	Ideal
Medium	100-400	30-60 min	Acceptable
Large	400+	1+ hour	Split if possible

PR Description Template

markdown

## Summary
Brief description of changes

## Changes
- Added X
- Modified Y
- Removed Z

## Testing
- [ ] Unit tests added
- [ ] Manual testing done

## Screenshots (if applicable)
[Before/After images]

## Related Issues
Closes #123

Release Management

Semantic Versioning

MAJOR.MINOR.PATCH
  │     │     │
  │     │     └── Bug fixes (backward compatible)
  │     └── New features (backward compatible)
  └── Breaking changes

Release Process

bash

# Create release branch
git checkout -b release/v1.2.0 develop

# Bump version, update changelog
# ... make changes ...

# Merge to main and tag
git checkout main
git merge release/v1.2.0
git tag -a v1.2.0 -m "Release v1.2.0"
git push origin main --tags

# Merge back to develop
git checkout develop
git merge release/v1.2.0

Changelog Format

markdown

# Changelog

## [1.2.0] - 2024-01-15
### Added
- OAuth2 authentication support

### Changed
- Improved error messages

### Fixed
- Memory leak in cache handler

### Deprecated
- Old authentication method (use OAuth2)

### Removed
- Legacy API v1 endpoints

Git Hooks

Common Hooks

Hook	Timing	Use Case
`pre-commit`	Before commit	Linting, formatting
`commit-msg`	After message	Validate message format
`pre-push`	Before push	Run tests
`post-merge`	After merge	Install dependencies

Example pre-commit

bash

#!/bin/sh
# .git/hooks/pre-commit

# Run linter
npm run lint
if [ $? -ne 0 ]; then
  echo "Linting failed. Please fix errors."
  exit 1
fi

# Run tests
npm test
if [ $? -ne 0 ]; then
  echo "Tests failed. Please fix before committing."
  exit 1
fi

Using Husky (Node.js)

json

// package.json
{
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged",
      "commit-msg": "commitlint -E HUSKY_GIT_PARAMS"
    }
  }
}

Troubleshooting

Common Issues

Problem	Solution
Accidental commit to main	`git reset HEAD~1` (before push)
Wrong branch	`git stash`, switch, `git stash pop`
Need to undo merge	`git revert -m 1 <merge-commit>`
Lost commits	`git reflog` to find, `git cherry-pick`
Large file committed	`git filter-branch` or BFG Repo-Cleaner

Recovery Commands

bash

# Undo last commit (keep changes)
git reset --soft HEAD~1

# Undo last commit (discard changes)
git reset --hard HEAD~1

# Recover deleted branch
git reflog
git checkout -b recovered-branch <sha>

# Undo a pushed commit (safe)
git revert <sha>

Anti-Patterns to Avoid

Force pushing to shared branches - Breaks others' history
Giant commits - Hard to review, hard to bisect
Vague commit messages - "fix" tells nothing
Long-lived branches - Merge conflict hell
Committing generated files - Bloats repo, causes conflicts
Committing secrets - Security risk (even after removal)
Rebasing public history - Breaks collaborators
Ignoring CI failures - Broken windows effect

Quick Reference

BRANCHES:
  main       → Production (protected)
  develop    → Integration (Git Flow)
  feature/*  → New work
  fix/*      → Bug fixes
  hotfix/*   → Production emergencies

COMMITS:
  feat(scope): add feature
  fix(scope): fix bug
  docs(scope): update docs
  refactor(scope): restructure code

DAILY FLOW:
  git checkout -b feature/ticket-desc
  git add -p && git commit
  git rebase origin/main
  git push -u origin feature/ticket-desc

VERSIONING:
  MAJOR.MINOR.PATCH
  Breaking.Feature.Bugfix

Files

Just SKILL.md in skills/managing-git of CloudAI-X/opencode-workflow.

Open the folder on GitHubat commit 0128ca6

Compare with similar skills

Managing Git 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.

Managing Git compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Managing Git this skillCloudAI-X/opencode-workflow	275	—	~2.5k	Automated safety check: Pass	MIT	9 mo ago
ToolJet Multi-Repo CommitToolJet/ToolJet	41k	—	~1.3k	Automated safety check: Pass	AGPL-3.0	today
Git Workflow and Versioningaddyosmani/agent-skills	103k	2 repos	~3.5k	Automated safety check: Notes	MIT	4 days ago
React Router Pull Request Creatorremix-run/react-router	57k	—	~2.5k	Automated safety check: Pass	MIT	yesterday
Saleor Commit Workflowsaleor/saleor	23k	—	~575	Automated safety check: Pass	BSD-3-Clause	yesterday
Emoji Commit ConventionsbaptisteArno/typebot.io	11k	—	~424	Automated safety check: Pass	Custom licence	yesterday

Similar skills

ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
41k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
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.
103k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes
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.
57k GitHub stars~2.5k tokensUpdated yesterday
DevelopmentAuto-check passed
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
23k GitHub stars~575 tokensUpdated yesterday
DevelopmentAuto-check passed
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.
11k GitHub stars~424 tokensUpdated yesterday
DevelopmentAuto-check passed
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.
3.2k GitHub stars~881 tokensUpdated today
DevelopmentAuto-check: notes

Questions about Managing Git

What does Managing Git do?

Guides git workflows, branching strategies, commit conventions, and version control best practices. Managing Git is an agent skill from CloudAI-X/opencode-workflow. Guides git workflows, branching strategies, commit conventions, and version control best practices.

When should I use Managing Git?

Managing Git fits situations like: managing repositories; creating branches; handling merges.

How do I install Managing Git in Claude Code?

Run `npx skills add CloudAI-X/opencode-workflow --skill managing-git -a claude-code`. Or copy the skill folder (skills/managing-git in CloudAI-X/opencode-workflow) into .claude/skills/managing-git in your project. Claude Code loads it when a task matches its description.

How do I install Managing Git in Codex?

Run `npx skills add CloudAI-X/opencode-workflow --skill managing-git -a codex`. Or copy the skill folder (skills/managing-git in CloudAI-X/opencode-workflow) into .agents/skills/managing-git in your project. Codex loads it when a task matches its description.

Can I use Managing Git 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 CloudAI-X/opencode-workflow --skill managing-git -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-git, .gemini/skills/managing-git, .github/skills/managing-git and .opencode/skills/managing-git in your project.

What does Managing Git need to run?

Going by SKILL.md and its folder, Managing Git needs the command-line tools its instructions call (git and npm). Our summary lists: Node.js. Compatibility (from SKILL.md): opencode.

Does Managing Git access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Managing Git 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 Managing Git use?

Managing Git is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Managing Git use?

About 2.5k tokens (SKILL.md is roughly 10k 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 Managing Git?

Skills that share tags, products or a category with Managing Git: ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Saleor Commit Workflow (saleor/saleor, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Managing Git?

CloudAI-X (a GitHub user) maintains it in CloudAI-X/opencode-workflow, which has 275 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on January 10, 2026.

Source: CloudAI-X/opencode-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Managing Git

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Managing Git

When to Use This Skill

Branching Strategies

Git Flow

GitHub Flow

Trunk-Based Development

Commit Message Conventions

Conventional Commits

Types

Good vs Bad Commits

Commit Body Guidelines

Branch Naming Conventions

Pattern

Examples

Branch Rules

Git Workflow Commands

Daily Workflow

Useful Commands

Cleanup Commands

Handling Conflicts

Conflict Resolution Flow

Prevention Strategies

Pull Request Best Practices

PR Checklist

PR Size Guidelines

PR Description Template

Release Management

Semantic Versioning

Release Process

Changelog Format

Git Hooks

Common Hooks

Example pre-commit

Using Husky (Node.js)

Troubleshooting

Common Issues

Recovery Commands

Anti-Patterns to Avoid

Quick Reference

Files

Compare with similar skills

Similar skills

More from CloudAI-X/opencode-workflow

Related

Questions about Managing Git