What is the 'Technical correctness over social comfort' principle?

It is a core philosophy that prioritizes substantive technical analysis and honest feedback over superficial politeness to ensure the highest possible code quality.

Can I use this skill to prepare my own code for review?

Yes, it includes a PR description template and a 'Verification Before Claiming Done' checklist to help you self-review your code before submission.

How does this skill help with security?

The skill includes a specific security verification step in its checklist, prompting reviewers to check for injection vulnerabilities, authentication issues, and exposed secrets.

How are code issues categorized by this skill?

Issues are categorized into four levels: Critical (security/crashes), Important (bugs/performance), Minor (style/improvements), and Nitpick (personal preference).

Code Review Workflow

Name: Code Review Workflow
Author: timequity

bytimequity

Collaboration Tools

Standardizes the code review process through technical checklists, severity grading, and professional feedback templates.

About

The craft-coder code-review skill transforms how developers interact with Pull Requests by prioritizing technical correctness over social comfort. It provides a comprehensive framework for reviewing code, including a six-point verification checklist covering logic, security, and maintainability. By offering clear severity levels for issues and structured templates for giving and receiving feedback, it ensures that code reviews are objective, thorough, and actionable, helping teams maintain high standards without the friction of vague communication.

Key Features

Built-in PR description templates and git diff commands
Professional guidelines for receiving and responding to feedback
Comprehensive 6-point technical verification checklist
0 GitHub stars
Structured feedback templates for issue description and suggestions
Categorized issue severity levels from Critical to Nitpick

Use Cases

Preparing your own code changes for a formal review process
Standardizing feedback quality and communication across an engineering team
Conducting a thorough technical review of a colleague's Pull Request

About

Key Features

Built-in PR description templates and git diff commands
Professional guidelines for receiving and responding to feedback
Comprehensive 6-point technical verification checklist
0 GitHub stars
Structured feedback templates for issue description and suggestions
Categorized issue severity levels from Critical to Nitpick

Use Cases

Preparing your own code changes for a formal review process
Standardizing feedback quality and communication across an engineering team
Conducting a thorough technical review of a colleague's Pull Request