You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLAUDE.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ When working on ty, PR titles should start with `[ty]` and be tagged with the `t
65
65
- All changes must be tested. If you're not testing your changes, you're not done.
66
66
- Get your tests to pass. If you didn't run the tests, your code does not work.
67
67
- Follow existing code style. Check neighboring files for patterns.
68
-
- Always run `uvx pre-commit run -a` at the end of a task.
68
+
- Always run `uvx prek run -a` at the end of a task.
69
69
- Avoid writing significant amounts of new code. This is often a sign that we're missing an existing method or mechanism that could help solve the problem. Look for existing utilities first.
70
70
- Avoid falling back to patterns that require `panic!`, `unreachable!`, or `.unwrap()`. Instead, try to encode those constraints in the type system.
71
71
- Prefer let chains (`if let` combined with `&&`) over nested `if let` statements to reduce indentation and improve readability.
0 commit comments