Dashboard › craft › Prefer minimal, fail-closed fixes backe…
01a08148-9a52-79f4-b7e5-e8752964fd08| Project | Hits | Last recalled |
|---|---|---|
| opencode-lore | 1 | 15h ago |
When reviewing or fixing PR feedback, first inspect the relevant source, review threads, branch state, and recent changes rather than making broad assumptions. Implement only the narrowly justified correction, preserving valid existing behavior unless evidence shows it is obsolete. For parsing, discovery, documentation, and workflow boundaries, prefer fail-closed handling: treat missing markers, malformed or blank output, and absent required paths as explicit contextual errors. Add focused regression coverage before or alongside fixes, then run verification and a final review.