15 lines
501 B
Markdown
15 lines
501 B
Markdown
# Task Templates
|
|
|
|
## Bugfix
|
|
1. Read the affected package and nearby tests
|
|
2. Explain root cause briefly
|
|
3. Implement the smallest fix in the narrowest package possible
|
|
4. Run focused validation, then `go test ./...` if appropriate
|
|
5. Report risks, especially around concurrency and I/O
|
|
|
|
## Refactor
|
|
1. Preserve public behavior
|
|
2. Avoid package-wide churn unless clearly justified
|
|
3. Keep imports, naming, and package boundaries tidy
|
|
4. Re-run tests after each meaningful step if the refactor is risky
|