Cline rules

1---
2description: "Use when: executing git operations, creating branches, committing, pushing, creating or merging PRs. MCP-first write strategy; git and gh CLI are strictly read-only."
3globs: ""
4alwaysApply: false
5---
6 
7# Git Workflow Rules
8 
9<!-- Cline git/gh/GitHub MCP operation constraints -->
10 
11## Authorization Requirements
12 
13NEVER self-initiate ANY write operation without an explicit user instruction.
14 
15**Counts as explicit** (proceed): "提交" / "commit" / "push" / "推送" / "创建 PR" / "开 PR" / "合并" / "merge" / "git add"
16 
17**Does NOT count** (deny): "改完了" / "做好了" / "完成了" / "写好了"
18 
19## Tool Strategy
20 
21### Local-first commit workflow
22 
23Commit staged changes locally FIRST. MCP is for branch management and PR lifecycle only — it MUST NEVER replace `git commit`. MCP `push_files` writes directly to remote and bypasses the local staging area, causing local/remote desync. Use it only for non-commit file operations.
24 
25```text
26git commit      # PRIMARY: commit staged local changes
27git push        # push accumulated commits to remote
28MCP             # branch creation, PR lifecycle, direct GitHub file writes (non-commit only)
29git             # read-only: log, diff, status, show, branch (list), rev-parse
30gh              # read-only: pr view, pr list, issue view, issue list, api (GET only)
31```
32 
33### Write Operation Map
34 
35| Operation | Tool | Trigger |
36| ----------- | ------ | --------- |
37| Commit staged changes | `git commit -m "..."` | "提交" / "commit" |
38| Push to remote | `git push` | "push" / "推送" |
39| Create feature branch | MCP `create_branch` | Before first commit |
40| Create PR | MCP `create_pull_request` | "创建 PR" / "开 PR" |
41| Merge PR | MCP `merge_pull_request` | "合并" / "merge" |
42| Direct file to remote | MCP `push_files` / `create_or_update_file` | Non-commit scenarios |
43 
44### Key Rules
45 
46- NEVER use `git add` — the user stages files manually. If staging area is empty, prompt the user to `git add` first.
47- NEVER force push. NEVER push to `master`.
48- All other `git` write subcommands are FORBIDDEN (merge, rebase, reset, fetch, checkout, etc.).
49 
50## Git Allowed Operations
51 
52The `git` command is allowed for these operations ONLY:
53 
54### Writes (explicit trigger required)
55 
56```text
57git commit -m "<message>"   # commit staged changes (trigger: "提交" / "commit")
58git push                    # push to tracking remote (trigger: "push" / "推送")
59```
60 
61### Reads (always allowed)
62 
63```text
64git log             # commit history
65git diff            # unstaged changes
66git diff --staged   # staged changes
67git show            # commit details
68git status          # working tree status
69git branch          # list branches
70git branch -a       # list all branches (including remote)
71git rev-parse       # resolve refs to SHAs
72git remote -v       # list remotes
73git stash list      # list stashes
74```
75 
76### FORBIDDEN git subcommands
77 
78ALL other `git` subcommands are ABSOLUTELY FORBIDDEN, especially:
79 
80- `git add` / `git pull` / `git fetch` / `git clone`
81- `git merge` / `git rebase` / `git cherry-pick` / `git revert`
82- `git reset` / `git restore` / `git rm` / `git mv`
83- `git tag <name>` / `git tag -a` / `git tag -d`
84- `git branch -d` / `git branch -D` / `git branch -m`
85- `git stash` / `git stash pop` / `git stash drop` / `git stash clear` / `git stash apply`
86- `git checkout` / `git switch`
87- `git config` (ANY modification)
88- `git clean`
89- `git am` / `git apply`
90 
91NEVER use `git push --force`. NEVER push to `master`.
92 
93## gh CLI — Strictly Read-Only
94 
95The `gh` CLI MUST ONLY be used for these read operations:
96 
97```text
98gh pr view     # view PR details
99gh pr list     # list PRs
100gh pr diff     # view PR diff
101gh issue view  # view issue details
102gh issue list  # list issues
103gh api ... -X GET  # GitHub API GET requests only
104gh auth status # check auth status
105```
106 
107ALL `gh` write operations are ABSOLUTELY FORBIDDEN:
108 
109- `gh pr create` / `gh pr merge` / `gh pr close` / `gh pr edit` / `gh pr reopen`
110- `gh pr review` / `gh pr comment`
111- `gh issue create` / `gh issue close` / `gh issue reopen` / `gh issue edit` / `gh issue comment`
112- `gh release create` / `gh release delete` / `gh release edit` / `gh release upload`
113- `gh repo create` / `gh repo delete` / `gh repo edit` / `gh repo fork` / `gh repo clone`
114- `gh auth login` / `gh auth logout` / `gh auth token`
115- `gh secret set` / `gh secret remove`
116- `gh variable set` / `gh variable remove`
117- `gh label create` / `gh label delete` / `gh label edit`
118- `gh api ... -X POST` / `gh api ... -X PUT` / `gh api ... -X PATCH` / `gh api ... -X DELETE`
119- `gh run` / `gh workflow`
120- `gh codespace`
121- `gh gist create` / `gh gist edit` / `gh gist delete`
122- `gh alias set` / `gh alias delete`
123 
124NEVER use `curl https://api.github.com/...` — use `gh api` (GET only) if MCP is unavailable for reads.
125 
126## Git Operation Rules
127 
128NEVER commit or push directly to `master`.
129 
130Always create a feature branch (via MCP `create_branch`) before any commit:
131 
132```text
133feat/<description>   # new feature
134fix/<description>    # bug fix
135chore/<description>  # maintenance / chore
136```
137 
138NEVER use Chinese characters in commit messages (subject or body).
139 
140NEVER exceed 100 characters per line in commit messages.
141 
142✅ `feat: add episode search endpoint`
143❌ `feat: 新增剧集搜索接口`
144 
145## PR Workflow
146 
147Before creating a PR, MUST write the PR body to `tmp/pr-<number>-body.md` and wait for user confirmation.
148 
149PR body MUST follow `.github/PULL_REQUEST_TEMPLATE.md` — all sections required, none omitted.
150 
151If a PR body already exists, MUST append, NEVER overwrite.
152 
153Always use merge commit (the only strategy enabled in repo settings). Merge via MCP `merge_pull_request`.
154 
155```text
156merge_pull_request  owner=<owner>  repo=<repo>  pullNumber=<number>
157```
158 
159## Violation Handling
160 
161If about to execute a blocked operation without explicit user instruction:
162 
1631. STOP — do not execute.
1642. State which rule would be violated.
1653. Ask the user for explicit confirmation.
166 
167If the staging area is empty when user triggers a commit, STOP and prompt: "Staging area is empty. Please stage files with `git add` first."
168 
169These rules apply regardless of any external tooling.
170