Agent skill

Git Workflow

by affaan-m in affaan-m/ECC

Git工作流模式,包括分支策略、提交约定、合并与变基、冲突解决以及适用于各种规模团队的协作开发最佳实践. An agent skill from affaan-m/ECC.

MITAuto-check: notesDevelopment

Install Git Workflow

skills CLI
$ npx skills add affaan-m/ECC --skill git-workflow -a claude-code

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

GitHub CLI
$ gh skill install affaan-m/ECC git-workflow --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/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/zh-CN/skills/git-workflow .claude/skills/git-workflow && 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/

Facts

Skill name
git-workflow
GitHub stars
275k
Token cost
~2.9k tokens
SKILL.md length
329 words
Files
1
Skills in repo
645
Repo updated
First seen
Licence
MIT

At a glance

Git工作流模式,包括分支策略、提交约定、合并与变基、冲突解决以及适用于各种规模团队的协作开发最佳实践. An agent skill from affaan-m/ECC.

  • Tasks that involve Git workflow
  • SKILL.md covers 何时启用, 分支策略, 提交信息 and 合并 vs 变基, plus 4 more sections
  • Calls git, npm and npx; reaches github.com

What it does

Git Workflow is an agent skill from affaan-m/ECC. Git工作流模式,包括分支策略、提交约定、合并与变基、冲突解决以及适用于各种规模团队的协作开发最佳实践。

Its SKILL.md is about 2.9k 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. It works with Git and GitHub. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • Tasks that involve Git workflow

Example prompts

  • “/git-workflow”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit ef648e0. 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
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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 2.9k tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 329 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:526
    .env
  • NoteMentions a .env fileSKILL.md:527
    .env.local
  • NoteMentions a .env fileSKILL.md:528
    .env.*.local
  • NoteMentions a .env fileSKILL.md:673
    git add .env  # 包含API密钥

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 affaan-m/ECC at commit ef648e0, republished under its MIT licence (© affaan-m). 329 words, ~2,858 tokens.

Download SKILL.mdSave it as .claude/skills/git-workflow/SKILL.md (or your agent's skills folder).
name
git-workflow
description
Git工作流模式,包括分支策略、提交约定、合并与变基、冲突解决以及适用于各种规模团队的协作开发最佳实践。
origin
ECC

Git 工作流模式

Git 版本控制、分支策略与协作开发的最佳实践。

何时启用

  • 为新项目设置 Git 工作流
  • 决定分支策略(GitFlow、主干开发、GitHub Flow)
  • 编写提交信息和 PR 描述
  • 解决合并冲突
  • 管理发布和版本标签
  • 让新团队成员熟悉 Git 实践

分支策略

GitHub Flow(简单,推荐大多数场景使用)

最适合持续部署以及中小型团队。

main (protected, always deployable)
  │
  ├── feature/user-auth      → PR → merge to main
  ├── feature/payment-flow   → PR → merge to main
  └── fix/login-bug          → PR → merge to main

规则:

  • main 始终可部署
  • 从 main 创建功能分支
  • 准备就绪后发起 Pull Request
  • 审核通过且 CI 通过后,合并到 main
  • 合并后立即部署
主干开发(高速度团队)

最适合具备强大 CI/CD 和功能开关的团队。

main (主干)
  │
  ├── 短期功能分支(最长1-2天)
  ├── 短期功能分支
  └── 短期功能分支

规则:

  • 所有人直接提交到 main 或使用极短生命周期的分支
  • 功能开关隐藏未完成的工作
  • 合并前必须通过 CI
  • 每天多次部署
GitFlow(复杂,基于发布周期)

适合计划性发布和企业级项目。

main (生产发布版本)
  │
  └── develop (集成分支)
        │
        ├── feature/user-auth
        ├── feature/payment
        │
        ├── release/1.0.0    → 合并到 main 和 develop
        │
        └── hotfix/critical  → 合并到 main 和 develop

规则:

  • main 仅包含生产就绪代码
  • develop 是集成分支
  • 功能分支从 develop 创建,合并回 develop
  • 发布分支从 develop 创建,合并到 main 和 develop
  • 热修复分支从 main 创建,合并到 main 和 develop
何时使用哪种策略
策略团队规模发布频率最佳适用场景
GitHub Flow任意持续SaaS、Web 应用、初创公司
主干开发5 人以上有经验每天多次高速度团队、功能开关
GitFlow10 人以上计划性企业、受监管行业

提交信息

常规提交格式
<type>(<scope>): <subject>

[optional body]

[optional footer(s)]
类型
类型用途示例
feat新功能feat(auth): add OAuth2 login
fix错误修复fix(api): handle null response in user endpoint
docs文档docs(readme): update installation instructions
style格式调整,无代码变更style: fix indentation in login component
refactor代码重构refactor(db): extract connection pool to module
test添加/更新测试test(auth): add unit tests for token validation
chore维护任务chore(deps): update dependencies
perf性能改进perf(query): add index to users table
ciCI/CD 变更ci: add PostgreSQL service to test workflow
revert回滚之前的提交revert: revert "feat(auth): add OAuth2 login"
好与坏的示例
# 不好:模糊,无上下文
git commit -m "修复了一些东西"
git commit -m "更新"
git commit -m "进行中"

# 好:清晰,具体,解释原因
git commit -m "fix(api): 在 503 服务不可用时重试请求

外部 API 在高峰时段偶尔会返回 503 错误。
添加了指数退避重试逻辑,最多尝试 3 次。

关闭 #123"
提交信息模板

在仓库根目录创建 .gitmessage:

# <type>(<scope>): <subject>
# # 类型:feat, fix, docs, style, refactor, test, chore, perf, ci, revert
# 范围:api, ui, db, auth 等
# 主题:祈使语气,无句号,最多50个字符
#
# [可选正文] - 解释原因,而非内容
# [可选脚注] - 破坏性变更,关闭 #issue

启用方式:git config commit.template .gitmessage

合并 vs 变基

合并(保留历史)
bash
# Creates a merge commit
git checkout main
git merge feature/user-auth

# Result:
# *   merge commit
# |\
# | * feature commits
# |/
# * main commits

适用场景:

  • 将功能分支合并到 main
  • 希望保留完整历史
  • 多人共同开发该分支
  • 分支已推送,其他人可能基于它开展工作
变基(线性历史)
bash
# Rewrites feature commits onto target branch
git checkout feature/user-auth
git rebase main

# Result:
# * feature commits (rewritten)
# * main commits

适用场景:

  • 用最新的 main 更新本地功能分支
  • 希望获得线性、干净的历史
  • 分支仅存在于本地(未推送)
  • 只有你一个人在该分支上工作
变基工作流
bash
# Update feature branch with latest main (before PR)
git checkout feature/user-auth
git fetch origin
git rebase origin/main

# Fix any conflicts
# Tests should still pass

# Force push (only if you're the only contributor)
git push --force-with-lease origin feature/user-auth
何时不应变基
# 切勿变基以下分支:
- 已推送至共享仓库的分支
- 他人已基于其工作的分支
- 受保护分支(main、develop)
- 已合并的分支

# 原因:变基会重写历史,破坏他人的工作

Pull Request 工作流

PR 标题格式
<type>(<scope>): <description>

示例:
feat(auth): add SSO support for enterprise users
fix(api): resolve race condition in order processing
docs(api): add OpenAPI specification for v2 endpoints
PR 描述模板
markdown
## 内容

简要描述此 PR 的内容。

## 动机

解释动机和背景。

## 实现方式

值得强调的关键实现细节。

## 测试

- [ ] 新增/更新单元测试
- [ ] 新增/更新集成测试
- [ ] 执行手动测试

## 截图(如适用)

UI 变更的前后对比截图。

## 检查清单

- [ ] 代码遵循项目风格指南
- [ ] 完成自我审查
- [ ] 为复杂逻辑添加注释
- [ ] 更新文档
- [ ] 未引入新警告
- [ ] 测试在本地通过
- [ ] 关联问题已链接

关闭 #123
代码审查清单

审查者:

  • [ ] 代码是否解决了所述问题?
  • [ ] 是否处理了所有边界情况?
  • [ ] 代码是否可读且易于维护?
  • [ ] 是否有足够的测试?
  • [ ] 是否存在安全问题?
  • [ ] 提交历史是否干净(必要时已压缩)?

作者:

  • [ ] 在请求审查前已完成自我审查
  • [ ] CI 通过(测试、lint、类型检查)
  • [ ] PR 大小合理(理想情况下 <500 行)
  • [ ] 与单个功能/修复相关
  • [ ] 描述清晰解释了变更内容

冲突解决

识别冲突
bash
# Check for conflicts before merge
git checkout main
git merge feature/user-auth --no-commit --no-ff

# If conflicts, Git will show:
# CONFLICT (content): Merge conflict in src/auth/login.ts
# Automatic merge failed; fix conflicts and then commit the result.
解决冲突
bash
# See conflicted files
git status

# View conflict markers in file
# <<<<<<< HEAD
# content from main
# =======
# content from feature branch
# >>>>>>> feature/user-auth

# Option 1: Manual resolution
# Edit file, remove markers, keep correct content

# Option 2: Use merge tool
git mergetool

# Option 3: Accept one side
git checkout --ours src/auth/login.ts    # Keep main version
git checkout --theirs src/auth/login.ts  # Keep feature version

# After resolving, stage and commit
git add src/auth/login.ts
git commit
冲突预防策略
bash
# 1. Keep feature branches small and short-lived
# 2. Rebase frequently onto main
git checkout feature/user-auth
git fetch origin
git rebase origin/main

# 3. Communicate with team about touching shared files
# 4. Use feature flags instead of long-lived branches
# 5. Review and merge PRs promptly

分支管理

命名规范
# 功能分支
feature/user-authentication
feature/JIRA-123-payment-integration

# 错误修复
fix/login-redirect-loop
fix/456-null-pointer-exception

# 热修复(生产问题)
hotfix/critical-security-patch
hotfix/database-connection-leak

# 发布版本
release/1.2.0
release/2024-01-hotfix

# 实验/概念验证
experiment/new-caching-strategy
poc/graphql-migration
分支清理
bash
# Delete local branches that are merged
git branch --merged main | grep -v "^\*\|main" | xargs -n 1 git branch -d

# Delete remote-tracking references for deleted remote branches
git fetch -p

# Delete local branch
git branch -d feature/user-auth  # Safe delete (only if merged)
git branch -D feature/user-auth  # Force delete

# Delete remote branch
git push origin --delete feature/user-auth
暂存工作流
bash
# Save work in progress
git stash push -m "WIP: user authentication"

# List stashes
git stash list

# Apply most recent stash
git stash pop

# Apply specific stash
git stash apply stash@{2}

# Drop stash
git stash drop stash@{0}

发布管理

语义化版本
MAJOR.MINOR.PATCH

MAJOR:破坏性变更
MINOR:新功能,向后兼容
PATCH:错误修复,向后兼容

示例:
1.0.0 → 1.0.1(补丁:错误修复)
1.0.1 → 1.1.0(次要:新功能)
1.1.0 → 2.0.0(主要:破坏性变更)
创建发布
bash
# Create annotated tag
git tag -a v1.2.0 -m "Release v1.2.0

Features:
- Add user authentication
- Implement password reset

Fixes:
- Resolve login redirect issue

Breaking Changes:
- None"

# Push tag to remote
git push origin v1.2.0

# List tags
git tag -l

# Delete tag
git tag -d v1.2.0
git push origin --delete v1.2.0
变更日志生成
bash
# Generate changelog from commits
git log v1.1.0..v1.2.0 --oneline --no-merges

# Or use conventional-changelog
npx conventional-changelog -i CHANGELOG.md -s

Git 配置

基本配置
bash
# User identity
git config --global user.name "Your Name"
git config --global user.email "your@email.com"

# Default branch name
git config --global init.defaultBranch main

# Pull behavior (rebase instead of merge)
git config --global pull.rebase true

# Push behavior (push current branch only)
git config --global push.default current

# Auto-correct typos
git config --global help.autocorrect 1

# Better diff algorithm
git config --global diff.algorithm histogram

# Color output
git config --global color.ui auto
实用别名
bash
# Add to ~/.gitconfig
[alias]
    co = checkout
    br = branch
    ci = commit
    st = status
    unstage = reset HEAD --
    last = log -1 HEAD
    visual = log --oneline --graph --all
    amend = commit --amend --no-edit
    wip = commit -m "WIP"
    undo = reset --soft HEAD~1
    contributors = shortlog -sn
Gitignore 模式
gitignore
# Dependencies
node_modules/
vendor/

# Build outputs
dist/
build/
*.o
*.exe

# Environment files
.env
.env.local
.env.*.local

# IDE
.idea/
.vscode/
*.swp
*.swo

# OS files
.DS_Store
Thumbs.db

# Logs
*.log
logs/

# Test coverage
coverage/

# Cache
.cache/
*.tsbuildinfo

常见工作流

开始新功能
bash
# 1. Update main branch
git checkout main
git pull origin main

# 2. Create feature branch
git checkout -b feature/user-auth

# 3. Make changes and commit
git add .
git commit -m "feat(auth): implement OAuth2 login"

# 4. Push to remote
git push -u origin feature/user-auth

# 5. Create Pull Request on GitHub/GitLab
用新变更更新 PR
bash
# 1. Make additional changes
git add .
git commit -m "feat(auth): add error handling"

# 2. Push updates
git push origin feature/user-auth
同步 Fork 与上游
bash
# 1. Add upstream remote (once)
git remote add upstream https://github.com/original/repo.git

# 2. Fetch upstream
git fetch upstream

# 3. Merge upstream/main into your main
git checkout main
git merge upstream/main

# 4. Push to your fork
git push origin main
撤销错误操作
bash
# Undo last commit (keep changes)
git reset --soft HEAD~1

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

# Undo last commit pushed to remote
git revert HEAD
git push origin main

# Undo specific file changes
git checkout HEAD -- path/to/file

# Fix last commit message
git commit --amend -m "New message"

# Add forgotten file to last commit
git add forgotten-file
git commit --amend --no-edit

Git 钩子

预提交钩子
bash
#!/bin/bash
# .git/hooks/pre-commit

# Run linting
npm run lint || exit 1

# Run tests
npm test || exit 1

# Check for secrets
if git diff --cached | grep -E '(password|api_key|secret)'; then
    echo "Possible secret detected. Commit aborted."
    exit 1
fi
预推送钩子
bash
#!/bin/bash
# .git/hooks/pre-push

# Run full test suite
npm run test:all || exit 1

# Check for console.log statements
if git diff origin/main | grep -E 'console\.log'; then
    echo "Remove console.log statements before pushing."
    exit 1
fi

反模式

# 错误:直接提交到主分支
git checkout main
git commit -m "修复bug"

# 正确:使用功能分支和拉取请求

# 错误:提交机密信息
git add .env  # 包含API密钥

# 正确:添加到.gitignore,使用环境变量

# 错误:巨大的拉取请求(超过1000行)
# 正确:拆分为更小、更聚焦的拉取请求

# 错误:"更新"类提交信息
git commit -m "更新"
git commit -m "修复"

# 正确:描述性信息
git commit -m "fix(auth): 解决登录后的重定向循环问题"

# 错误:重写公共历史
git push --force origin main

# 正确:对公共分支使用回退
git revert HEAD

# 错误:长期存在的功能分支(数周/数月)
# 正确:保持分支短期(数天),频繁变基

# 错误:提交生成的文件
git add dist/
git add node_modules/

# 正确:添加到.gitignore

快速参考

任务命令
创建分支git checkout -b feature/name
切换分支git checkout branch-name
删除分支git branch -d branch-name
合并分支git merge branch-name
变基分支git rebase main
查看历史git log --oneline --graph
查看变更git diff
暂存变更git add . 或 git add -p
提交git commit -m "message"
推送git push origin branch-name
拉取git pull origin branch-name
暂存git stash push -m "message"
撤销上次提交git reset --soft HEAD~1
回滚提交git revert HEAD

© affaan-m, 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 docs/zh-CN/skills/git-workflow of affaan-m/ECC.

Open the folder on GitHubat commit ef648e0

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.

Git Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Workflow this skillaffaan-m/ECC275k—~2.9kAutomated safety check: NotesMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT
Create Pull Request with Work Item IDmakeplane/plane61k—~824Automated safety check: PassAGPL-3.0

Similar skills

  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed
  • Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    61k GitHub stars~824 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • 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

More from affaan-m/ECC

All 645 skills in this repo
  • Videodb

    affaan-m/ECC

    Ingest, index, search, edit, and monitor video and audio with the VideoDB Python SDK — upload from files, URLs, or RTSP feeds, build spoken and scene indexes with timestamped search and playable…

    275k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes
  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    275k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed
  • Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    275k GitHub stars~2.9k tokensUpdated 3 days ago
    Auto-check passed
  • Measures whether agents actually follow a skill, rule or agent definition by generating scenarios at three strictness levels and scoring tool-call traces.

    275k GitHub starsUsed in 1 repo~623 tokens
    Auto-check passed
  • Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

    275k GitHub stars~3.5k tokensUpdated 3 days ago
    Auto-check passed
  • Adds one optional external Codex critique that tries to break a council's decision draft, sent to OpenAI only after you consent.

    275k GitHub stars~1.5k tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Git Workflow

What does Git Workflow do?

Git工作流模式,包括分支策略、提交约定、合并与变基、冲突解决以及适用于各种规模团队的协作开发最佳实践. An agent skill from affaan-m/ECC. Git Workflow is an agent skill from affaan-m/ECC.

When should I use Git Workflow?

Git Workflow fits situations like: tasks that involve Git workflow.

How do I install Git Workflow in Claude Code?

Run `npx skills add affaan-m/ECC --skill git-workflow -a claude-code`. Or copy the skill folder (docs/zh-CN/skills/git-workflow in affaan-m/ECC) 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 affaan-m/ECC --skill git-workflow -a codex`. Or copy the skill folder (docs/zh-CN/skills/git-workflow in affaan-m/ECC) 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 affaan-m/ECC --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 (git, npm and npx). Our summary lists: Node.js.

Does Git Workflow access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Git Workflow safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. 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 2.9k tokens (SKILL.md is roughly 11k 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: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Release Bump (jamiepine/voicebox, 57k stars) and Creating Description For Gh PR (redis/jedis, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Workflow?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 275,023 GitHub stars. The repository holds 645 skills in this directory. The repository was last updated on October 5, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.