git-workflow

A set of Git rules for contributing to the open-source Qclaw project. It defines how to use forks and the main repository, name branches, format commits, and open pull requests.

In plain words
What is it for?
Use it when syncing your fork, creating branches, writing commits, or preparing a GitHub pull request for Qclaw.
Why use it?
It removes guesswork about the project's contribution process and keeps changes consistent and easy to review.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/qiuzhi2046/qclaw/git-workflow
Clone the repo
git clone --depth 1 https://github.com/qiuzhi2046/Qclaw

Made for: Cursor.

Per session 329 This file is loaded in full into every session.
When invoked 329 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00329 $0.00329
Opus 5 $0.00164 $0.00164
Sonnet 5 $0.00066 $0.00066
Haiku 4.5 $0.00033 $0.00033

Measured yesterday against content hash 7ba27fdf0012, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

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.

.cursor/rules/git-workflow.mdc · 51 lines

What it actually says

Git 工作流程

Remote 設定

Remote 指向 用途
origin JasonYang318/Qclaw(fork) 推送改動
upstream qiuzhi2046/Qclaw(原始) 同步最新版

同步上游

git fetch upstream
git checkout main
git merge upstream/main
git push origin main

分支命名

  • 新功能:feat/<功能名>
  • 修 bug:fix/<問題描述>
  • 文件:docs/<主題>

Commit 訊息格式

<type>: <簡述>
前綴 用途
feat 新功能
fix 修 bug
docs 文件變更
refactor 重構
test 測試
chore 工具 / 設定

PR 流程

  1. 先開 GitHub Issue,等維護者確認方向
  2. 在自己的 fork 分支開發
  3. 跑完三個驗證指令後再 commit
  4. 推送到 origin,開 PR 指向 qiuzhi2046/Qclaw
Changes

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.

  1. yesterday First seen · 51 lines · 329 tokens per session scan A 7ba27fdf0012

Subscribe to this mod's changes

git-workflow is a cursor rule published in the GitHub repository qiuzhi2046/Qclaw (2,818 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 329 tokens to every session, about $0.0016 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.