review

Review code for quality, specification compliance, and potential risks.

Updated Dec 28, 2023
One-click install
npx skills add https://github.com/daisuke-tanabe/daisuke-tanabe --skill review-daisuke-tanabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/daisuke-tanabe/daisuke-tanabe/tree/main/.claude/skills/review
Command: npx skills add https://github.com/daisuke-tanabe/daisuke-tanabe --skill review-daisuke-tanabe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code for quality, ensuring adherence to specifications, identifying potential risks, and verifying compliance with project conventions before commits or during pull requests.

Core Features & Use Cases

  • Pre-commit Checks: Perform a final review before committing code.
  • PR Reviews: Audit code quality within pull requests.
  • Code Audits: Assess the quality of existing codebase against defined standards.
  • Use Case: Before merging a new feature, use this skill to automatically check the relevant files for hardcoded secrets, ensure all tests pass, and verify adherence to the project's naming conventions.

Quick Start

Use the review skill to analyze the code in 'src/utils/helpers.ts'.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for pull requests and pre-commit checks?

Automated code review validates specification compliance, detects risks, and enforces project conventions during pre-commit checks or pull request reviews. It analyzes code against linting rules, type checking, and test execution.

Can I audit an existing codebase for quality and specification compliance?

Code audits assess existing codebase quality against defined project standards and conventions. This process identifies potential risks, validates type checking, and ensures existing files adhere to required specifications.

What is the best way to check for hardcoded secrets before merging a pull request?

Pre-merge quality assurance checks relevant files for hardcoded secrets, verifies test execution, and confirms adherence to naming conventions. This automated review ensures code meets all project specifications before integration.

Does code review work with linting rules and type checking for pre-commit validation?

Pre-commit validation applies linting rules and type checking to ensure code quality before changes are committed. The review process validates code against these project conventions and identifies potential risks.

How do I perform a final review before committing code to ensure quality?

A final pre-commit review checks code quality, specification compliance, and potential risks before committing changes. It validates code against project conventions, linting rules, and executes tests to ensure reliability.

What are the limitations of automated code quality assurance for pull requests?

Automated code quality assurance validates linting, type checking, test execution, and convention compliance, but requires defined project standards to function. Manual intervention may still be needed for complex architectural risk assessment.