skills.rest
timequity
timequityOFFICIAL
Explore all skills by this author →
GitHub

code-review

Review pull requests for correctness, security, tests, readability, and maintainability.

6|Updated Dec 7, 2025
Search Tags:#security#patterns#quality#PR review#code-review
One-click install
npx skills add https://github.com/timequity/plugins --skill code-review-timequity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/timequity/plugins/tree/main/craft-coder/code-review
Command: npx skills add https://github.com/timequity/plugins --skill code-review-timequity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Encapsulates code-review guidance and a checklist to ensure technical correctness and quality.

Core Features & Use Cases

  • Core review principles and checklists
  • Clear severity levels and actionable feedback
  • Practical examples for actionable improvements

Quick Start

Use the checklist to review a PR: verify logic, security, tests, readability, and patterns.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure code reviews to catch security issues and quality problems consistently?▼

Structured code reviews use checklists covering logic correctness, security vulnerabilities, test coverage, readability, and design patterns. This approach ensures consistent evaluation across PRs and languages, applying severity levels to each finding so teams prioritize fixes before merge.

What should I check when reviewing a pull request?▼

Review PRs against correctness, security, test coverage, readability, maintainability, and pattern consistency. Provide severity levels with concrete, actionable suggestions so developers understand what to fix and why before merging code.

Can code reviews work across different programming languages and project types?▼

Yes. Technical code-review principles apply universally across languages and project structures. Checklists for logic, security, tests, and patterns translate to any codebase, enabling consistent quality standards regardless of tech stack.

How do I give feedback that actually improves code?▼

Actionable feedback combines clear severity levels with concrete suggestions and verifiable checks. This guides developers on what changed and why, reducing review cycles and ensuring alignment with team standards before code reaches production.

What's the difference between unstructured and structured code reviews?▼

Unstructured reviews depend on reviewer expertise and mood; quality varies. Structured reviews use consistent checklists, defined severity levels, and concrete examples, ensuring every PR gets the same technical rigor and reducing inconsistent feedback.

Related Skills

Explore More Software Engineering Skills→
dokipendokipen
1

code-reviewer

Automate pull request code reviews across languages with structured criteria.

Community
Advanced
robertzengcnrobertzengcn

ship

Automate base branch merging, tests, version bumps, changelogs, and pull requests.

Community
Advanced
nishchaydevnishchaydev

lint-and-validate

Run linting, type checking, and security audits on Node.js/TypeScript and Python repositories.

Community
Intermediate
J03Fr0stJ03Fr0st

sonarqube-review

Analyze code for bugs, vulnerabilities, and code smells using SonarQube-like rules.

Community
Intermediate