What is collaboration?

Team-development rules for projects where multiple developers share code. They cover consistent coding, branches, commits, reviews, testing, and conflict handling.

Use it to guide Git branches and commit messages, code reviews, automated checks, testing, security checks, and communication in team or open-source projects.

Without shared working rules, developers can overwrite each other's work, skip checks, or merge changes that have not been reviewed.

collaboration — Cursor rule for Cursor by wangqiqi: Team-development rules for projects where multiple developers share code.

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/wangqiqi/cursor-ai-rules/collaboration

Clone the repo

git clone --depth 1 https://github.com/wangqiqi/cursor-ai-rules

Made for: Cursor.

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

README.md

[![agentmods](https://agentmods.dev/badge/rules/wangqiqi/cursor-ai-rules/collaboration.svg)](https://agentmods.dev/rules/wangqiqi/cursor-ai-rules/collaboration)

Your own site

<a href="https://agentmods.dev/rules/wangqiqi/cursor-ai-rules/collaboration"><img src="https://agentmods.dev/badge/rules/wangqiqi/cursor-ai-rules/collaboration.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 2,464 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.02464
Opus 5	$0.00000	$0.01232
Sonnet 5	$0.00000	$0.00493
Haiku 4.5	$0.00000	$0.00246

Measured 4d ago against content hash fbbd7fb52392, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

collaboration 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 4d 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.

.cursor/rules/team/collaboration.mdc · 318 lines

How it starts

The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.

👥 团队协作规则

版本: v4.3.0 | 最后更新: 2026-01-15 | 作者: wangqiqi (https://github.com/wangqiqi)

⚠️ 协作原则

MUST 遵循以下团队协作准则：

MUST 使用一致的代码风格和规范
NEVER 直接推送到主分支
ALWAYS 进行代码审查
DO NOT 跳过测试环节
MUST 及时同步和解决冲突
ALWAYS 保持沟通透明

🎯 适用场景

2人以上的开发团队
开源项目协作
企业级软件开发
分布式团队协作

📋 协作流程

Git 工作流

分支策略

main (或 master)          # 生产就绪分支
├── develop             # 开发主分支
│   ├── feature/*       # 功能分支
│   ├── bugfix/*        # 缺陷修复分支
│   ├── hotfix/*        # 紧急修复分支
│   └── release/*       # 发布分支

提交规范

# 格式: <type>(<scope>): <subject>
# 示例:
feat(auth): add JWT token authentication
fix(ui): resolve button alignment issue
docs(readme): update installation instructions
refactor(api): optimize database queries
test(auth): add unit tests for login function

提交类型

feat: 新功能
fix: 缺陷修复
docs: 文档更新
style: 代码格式调整
refactor: 代码重构
test: 测试相关
chore: 构建工具或辅助工具的变动

代码审查 (Code Review)

审查清单

功能完整性: 实现是否满足需求
代码质量: 遵循编码规范和最佳实践
测试覆盖: 是否有足够的测试用例
性能影响: 新代码是否影响系统性能
安全检查: 是否存在安全漏洞
文档更新: 相关文档是否已更新

审查流程

创建 PR/MR: 推送功能分支并创建合并请求
初步检查: 作者自查，运行测试套件
同行审查: 至少1-2名团队成员审查
自动化检查: CI/CD 流水线验证
批准合并: 审查通过后合并到目标分支

沟通规范

问题跟踪

<!-- GitHub Issue 模板 -->
## 问题描述
[清晰简洁的问题描述]

## 重现步骤
1. [第一步]
2. [第二步]
3. [第三步]

## 期望结果
[期望的正确行为]

## 实际结果
[当前的错误行为]

## 环境信息
- OS: [操作系统版本]
- Browser: [浏览器版本，如果适用]
- Version: [应用版本]

## 其他信息
[任何其他相关信息]

会议规范

站会: 15分钟，站立进行，汇报进展和障碍
计划会议: 梳理需求，估算工作量
回顾会议: 总结经验教训，持续改进
技术分享: 定期分享技术知识和经验

🏗️ 项目结构

共享项目布局

project/
├── src/                    # 源代码
│   ├── components/         # 可复用组件
│   ├── pages/             # 页面组件
│   ├── services/          # 业务服务
│   ├── utils/             # 工具函数
│   └── types/             # 类型定义
├── tests/                 # 测试文件
│   ├── unit/             # 单元测试
│   ├── integration/      # 集成测试
│   └── e2e/              # 端到端测试
├── docs/                  # 项目文档
│   ├── api/              # API文档
│   ├── guides/           # 使用指南
│   └── architecture/     # 架构文档
├── scripts/               # 构建和部署脚本
├── .github/               # GitHub 配置
│   ├── workflows/        # CI/CD 工作流
│   └── ISSUE_TEMPLATE/   # Issue 模板
└── .cursor/               # AI 协作配置

Read the full file on GitHub · 318 lines

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.

4d ago First seen · 318 lines · 0 tokens per session scan A fbbd7fb52392

Subscribe to this mod's changes

collaboration is a cursor rule published in the GitHub repository wangqiqi/cursor-ai-rules (15 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,464 tokens. 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.

Commits Git and workflow

collaboration