Borrowing it
Nothing to install: this file belongs to ZhuoZhuoCrayon/ai-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ZhuoZhuoCrayon/ai-workspace/main/.agents/skills/git-workflow/SKILL.mdgit clone --depth 1 https://github.com/ZhuoZhuoCrayon/ai-workspaceWrote 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/zhuozhuocrayon/ai-workspace/git-workflow)<a href="https://agentmods.dev/skills/zhuozhuocrayon/ai-workspace/git-workflow"><img src="https://agentmods.dev/badge/skills/zhuozhuocrayon/ai-workspace/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.
<a href="https://agentmods.dev/skills/zhuozhuocrayon/ai-workspace/git-workflow"><img src="https://agentmods.dev/badge/skills/zhuozhuocrayon/ai-workspace/git-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00145 | $0.01391 |
| Opus 5.5 | $0.00058 | $0.00556 |
| Sonnet 5.5 | $0.00029 | $0.00278 |
| Haiku 4.5 | $0.00015 | $0.00139 |
Grade A, and why
git-workflow 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 today.
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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git 提交规范
0x01 场景判断
先判断提交对象：
- 如果用户明确要求提交非工作区（知识库）的项目变更，按
0x02处理。 - 否则按工作区（知识库）变更提交处理，使用
0x03的规范。
不要因为变更路径看起来像某个项目，就自动切换到项目提交规范。
0x02 非工作区项目提交
进入目标项目后，遵循项目自身规范：
- 先读取项目
AGENTS.md。 - 查找并读取贡献者文档，例如
CONTRIBUTING.md。 - 查看项目提交历史，再起草分组方案和 commit message。
- 项目规范与工作区规范冲突时，以项目规范为准。
项目接入 PreCI 时，提交前执行 PreCI 配置准备。
0x03 工作区知识库提交
Commit message 遵循 Conventional Commits：<type>(<scope>): <subject>。
Scope 使用工作区约定：knowledge、skill、project、issue、rules。
- 当用户说“提交工作区变更”时，同时检查工作区根目录和
private/。根目录的改动按本段提交；private/有改动时按0x04提交。两边都有改动就各提一次。 - 本机和开发机都会推送同一条主干。提交前用 rebase 把当前分支接到远端，再创建新提交。
- 工作区不干净且 rebase 会改到这些文件时，先暂存改动，完成后再恢复。
- 这次同步不新增 merge commit。
git fetch origin
git rebase origin/main
分叉时改为：
git pull --rebase origin main
- 默认按变更主题拆分多个 commit，而不是合并成一个 commit。
- 分类优先按“为什么要改”分组，例如：
docs/rules、feat/skill、ci/tooling、chore/workspace。 - 工作区内存在来自不同会话的改动时，默认先确认范围，用户明确要求一起提交时可继续分类提交。
- 提交前先查看
git status、git diff HEAD和git log，再起草分组方案和 commit message。 - 同一 commit 只保留一个明确主题，避免把规则、脚本、知识文档和配置混在一起。
- 单组改动不足以独立提交时，可并入最接近主题的一组，但不能跨主题硬拼。
0x04 私有仓库提交
private/ 是独立的私有仓库，地址只记录在 private/repos.json。工作区 .gitignore 排除了它，根目录的 git status 看不到这里的文件。
用户说“提交工作区变更”，或明确要求提交 private/ 时，在 private/ 内执行：
git status
git diff HEAD
git log
提交前按 0x03 同步主干。私有仓主干是 master。
git fetch origin
git rebase origin/master
make private-pull 只做快进。不能快进时用上面的 rebase，再执行：
make private-push
按 0x03 的 Conventional Commits 和分组规则提交。作者使用该仓库已配置的 user.name 与 user.email。
git add <paths>
git commit -m "<type>(<scope>): <subject>"
提交后推送。另一台机器拉取：
make private-push
make private-pull
不要把 private/ 的文件放进工作区暂存区。private/ 没有自己的 AGENTS.md，不另读项目规范。
0x05 交付后的评审
用户要求交付 PR 或 MR 时，先完成目标项目自己的交付路径，再执行本节。
PR 或 MR 回读成功后：
- 按 code-review 审查这张 PR 或 MR。
- 把本次 review 建议发布到这张 PR 或 MR。
- 能在本任务里修复的问题留在同一分支修复，按原来的交付路径提交，然后重新审查。
- 达到可合并后停止。用户没有要求合并时，不合并。
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +2 lines df67adb17e99
- 13d ago Changed · +52 lines · +73 tokens per session d205a7a2f5cd
- 14d ago Changed · +29 lines b29fa948b2d9
- 2mo ago First seen · 46 lines · 72 tokens per session scan A 556eccdf0dde
git-workflow is a skill published in the GitHub repository ZhuoZhuoCrayon/ai-workspace (27 stars, last pushed today), licensed MIT. It adds 145 tokens to every session and 1,391 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…