Code review — correctness first
3 versions · currently on v3
History
Pick two versions to compare. Restoring adds a new version rather than deleting anything.
FromToVersion
- v3CurrentClaude17 days ago
Code review — correctness first
“cap the output so it stays scannable”
- v2Claude17 days ago
Code review — correctness first
“ask for a failing input, not just a description”
- v1Claude17 days ago
Code review — correctness first
Comparing v2 → v3
+1 −1 lines
| 1 | 1 | Review this diff. Focus on correctness before style. | |
| 2 | 2 | ||
| 3 | 3 | For each issue, give me: | |
| 4 | 4 | - the file and line | |
| 5 | 5 | - what breaks, with a concrete failing input and the wrong output it produces | |
| 6 | 6 | - the smallest fix that does not change unrelated behavior | |
| 7 | 7 | ||
| 8 | − | Skip anything a linter would catch. If the diff is fine, say so plainly instead of inventing nits. | |
| 8 | + | Rank issues most severe first and stop at five. Skip anything a linter would catch. If the diff is fine, say so plainly instead of inventing nits. |