code-review

Identify bugs, style violations, and defects in code changes during pull request reviews.

Updated Jun 26, 2025
One-click install
npx skills add https://github.com/williamjxj/friendshipdaycare --skill code-review-williamjxj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/williamjxj/friendshipdaycare/tree/main/.github/skills/code-review
Command: npx skills add https://github.com/williamjxj/friendshipdaycare --skill code-review-williamjxj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify bugs, style violations, and potential defects in code changes to improve reliability and maintainability.

Core Features & Use Cases

  • Checklist-driven reviews: Enforces consistent evaluation across correctness, readability, and maintainability.
  • Actionable feedback: Provides concrete suggestions to fix issues and improve design.
  • Use Case: During a PR review, apply a structured pass to catch edge cases and ensure adherence to project conventions.

Quick Start

Provide a concise, actionable code review for a pull request by identifying bugs, style issues, and improvement opportunities.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I identify bugs and style violations in a pull request?

To identify bugs and style violations in a pull request, apply a checklist-driven code review that evaluates correctness, readability, and maintainability. This structured pass catches edge cases and ensures adherence to project conventions.

What is the best way to provide actionable feedback during code reviews?

Actionable feedback during code reviews provides concrete suggestions to fix issues and improve design. It ensures recommendations are clear, traceable, and aligned with project conventions to improve overall reliability.

Does checklist-driven code review work for diverse languages and frameworks?

Checklist-driven code review works for diverse languages and frameworks by enforcing consistent evaluation across correctness and maintainability. It applies structured passes to catch edge cases regardless of the specific tech stack.

How do I ensure code changes adhere to project conventions?

To ensure code changes adhere to project conventions, perform a structured code review during pull requests. This enforces consistent evaluation and provides traceable recommendations aligned with your established standards.

Can static analysis improve code reliability and maintainability?

Static analysis improves code reliability and maintainability by identifying potential defects in code changes. Applying this during pull request reviews ensures feedback is clear and actionable, preventing bugs before merging.

Why should I use a structured pass to catch edge cases in code changes?

You should use a structured pass to catch edge cases because it enforces consistent evaluation across correctness, readability, and maintainability. This ensures potential defects are identified with traceable, actionable recommendations.