Skip to content

Commit 5911372

Browse files
authored
Update copilot-instructions.md (#878)
1 parent 9f11bef commit 5911372

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

.github/copilot-instructions.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -148,3 +148,25 @@ pnpm run coverage # Generate coverage reports
148148
- The code is developed and maintained by developers based in Mainland China.
149149
- Comments should preferably be written in Simplified Chinese.
150150
- The user interface supports multiple languages, with English set as the default for global users.
151+
152+
## PR Review Policy
153+
154+
When performing Pull Request (PR) reviews, Copilot must always conduct a **comprehensive and independent review** of the entire PR content.
155+
156+
- **Full Review Every Time**
157+
Always review **all modified files** in every PR, regardless of previous reviews or user comments. Even during re-reviews, treat the PR as new and **do not rely on prior review states**.
158+
159+
- **No Skipping of Files**
160+
Do not skip or ignore any text-based file types (including `.md`, `.json`, `.yml`, `.toml`, `.ts`, `.js`, `.py`, `.html`, `.css`, `.tsx`, `.vue`, `.sh`, etc.). Every file that is changed must be fully examined.
161+
162+
- **Reference as Context Only**
163+
PR descriptions, commit messages, or user discussions serve only as **reference context**. The review must focus primarily on the **actual code and file changes**.
164+
165+
- **Infer Intent from Code Changes**
166+
Always attempt to **infer the purpose and intent** of the changes directly from the modified content, rather than relying solely on user statements or PR titles.
167+
168+
- **Critical Thinking Requirement**
169+
For each change, Copilot should assess correctness, consistency, and maintainability — ensuring that logic, style, and architectural impact align with project standards.
170+
171+
- **Independent Verification**
172+
Do not assume unchanged files or previously reviewed sections are safe; verify all code paths potentially affected by the modifications.

0 commit comments

Comments
 (0)