Keep CHECK work with the current owner - #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
修改内容
CHECK边界：开发中可直接确认的 N+1、循环 I/O、重复计算等问题保持当前 owner。ccdawn-bug-review触发条件，仅在已观察故障、正确性回归或根因不明时接管。原因
真实冒烟测试中，N+1 场景正确判定为
CHECK，但 primary 被误路由到ccdawn-bug-review。根因是“发现并修复问题”与 Bug skill 的触发描述存在重叠。影响
简单、明确的局部低效由当前开发 owner 直接修复和验证，不增加诊断、benchmark、规划或用户确认步骤。真实性能目标和故障诊断仍由各自专项 skill 负责。
验证
py -3 scripts\validate_ccdawn_skills.py --warnings-as-errorspy -3 -m unittest discover -s tests -p "test_*.py" -q.\install.ps1 -Agent codex-grok -VerifyOnlypy -3 scripts\run_brt_routing_eval.py --case feature-local-n-plus-one --reasoning-effort lowccdawn-bug-review或ccdawn-performance-engineering