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.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.00072 | $0.00538 |
| Opus 5 | $0.00036 | $0.00269 |
| Sonnet 5 | $0.00014 | $0.00108 |
| Haiku 4.5 | $0.00007 | $0.00054 |
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 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.
What it actually says
Git 提交规范
0x01 场景判断
先判断提交对象：
- 如果用户明确要求提交非工作区（知识库）的项目变更，按
0x02处理。 - 否则按工作区（知识库）变更提交处理，使用
0x03的规范。
不要因为变更路径看起来像某个项目，就自动切换到项目提交规范。
0x02 非工作区项目提交
进入目标项目后，遵循项目自身规范：
- 先读取项目
AGENTS.md。 - 查找并读取贡献者文档，例如
CONTRIBUTING.md。 - 查看项目提交历史，再起草分组方案和 commit message。
- 项目规范与工作区规范冲突时，以项目规范为准。
0x03 工作区知识库提交
Commit message 遵循 Conventional Commits：<type>(<scope>): <subject>。
Scope 使用工作区约定：knowledge、skill、project、issue、rules。
- 当用户说“提交工作区变更”时，默认按变更主题拆分多个 commit，而不是合并成一个 commit。
- 分类优先按“为什么要改”分组，例如：
docs/rules、feat/skill、ci/tooling、chore/workspace。 - 工作区内存在来自不同会话的改动时，默认先确认范围，用户明确要求一起提交时可继续分类提交。
- 提交前先查看
git status、git diff HEAD和git log，再起草分组方案和 commit message。 - 同一 commit 只保留一个明确主题，避免把规则、脚本、知识文档和配置混在一起。
- 单组改动不足以独立提交时，可并入最接近主题的一组，但不能跨主题硬拼。
0x04 输出约定
- 实际提交后说明 commit hash 与 message。
- 仅起草方案时输出分组方案与 commit message 草案。
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 · 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 7d ago), licensed MIT. It adds 72 tokens to every session and 538 once invoked, about $0.0004 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-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-next. 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.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…