mirror of
https://github.com/clash-verge-rev/clash-verge-rev.git
synced 2026-10-27 08:02:09 +08:00
chore: update pr-ai-slop-review
This commit is contained in:
@@ -81,6 +81,13 @@ If the PR references an issue, inspect that issue as well and compare the stated
|
||||
- Draft or vague "ongoing optimization" style PRs with broad churn and weak problem statement
|
||||
- Lint/Static Analysis Padding: The PR body includes exhaustive, unnecessary listings of "Lint" results, static analysis summaries, or tool outputs intended to pad the appearance of rigor without providing actual insight without explaining how these results directly relate to the reported issue.
|
||||
- Performative Verification/Testing: The PR contains elaborate "Verify" or "Test" sections that look structurally impressive (using templated checklists or fancy headers) but lack project-specific context, concrete reproduction steps, or meaningful assertions of correctness or where the 'Test' steps are just a generic echo of the implementation code..
|
||||
- Branch names that clearly match AI-agent workflow patterns, ephemeral execution IDs, or automated coding-session naming conventions.
|
||||
|
||||
## Hard Escalation Rules
|
||||
|
||||
- If the pull request branch name clearly appears to be generated by an AI coding workflow, autonomous coding agent, or mass-generated automation pipeline (for example: generic agent-run IDs, Copilot/Cursor/Windsurf/Codex/Claude Code style ephemeral task branches, or machine-formatted execution/session identifiers), treat the PR as likely-one-shot-ai with high confidence regardless of the diff quality or linked issue state.
|
||||
- This override exists because the submission flow itself indicates weak evidence of direct human ownership and iterative stewardship.
|
||||
Do not claim the PR is AI-generated as a fact unless explicitly disclosed. Frame conclusions in terms of likelihood and ownership-risk assessment.
|
||||
|
||||
## Counter-Signals
|
||||
|
||||
|
||||
Reference in New Issue
Block a user