task-reviewer-best-practices

Automate Go code review by running compilation, static analysis, and testing suites against code changes, then classifying problems into Critical, Major, Minor, or Positive categories to ensure quality assurance and best practices adherence.

The best way to classify issues during a Go task review is by categorizing them into Critical, Major, Minor, and Positive groups, which allows for easy prioritization of problems found during code analysis and automated checks.

Yes, you need golangci-lint and go vet to review Go best practices, as these tools perform the static analysis and linting required to identify architectural and syntactic issues before generating a structured review report.

Systematic task review handles code analysis by evaluating syntax, idioms, and architecture, and handles documentation generation by producing a detailed review report with actionable insights and classified recommendations for the completed task.

No, the task review workflow automatically identifies and reviews completed tasks specifically based on the run-task.md file structure, meaning this specific workflow format is required for proper task identification and systematic analysis.