reviewing-code

Reviews code quality, security, design, performance, and technical debt with Kotlin and TypeScript/React guardrails.

Updated Dec 15, 2019
One-click install
npx skills add https://github.com/matsuyoshi30/dotfiles --skill reviewing-code-matsuyoshi30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/matsuyoshi30/dotfiles/tree/main/.agents/skills/reviewing-code
Command: npx skills add https://github.com/matsuyoshi30/dotfiles --skill reviewing-code-matsuyoshi30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to perform comprehensive reviews that assess code quality, security, design, performance, technical debt, and intent alignment, ensuring changes meet quality standards before they are merged.

Core Features & Use Cases

  • Evaluates Code Quality & Maintainability across languages, flagging readability, naming, duplication, and test coverage.
  • Highlights Security vulnerabilities, including input validation, authorization, and dependency risks, with actionable guidance.
  • Enforces consistent Design Patterns & Architecture, SOLID adherence, and error handling, to improve maintainability and scalability.
  • Provides a structured methodology for reviews, including prioritized issue categorization (CRITICAL to LOW) and actionable recommendations.
  • Applies language-specific guardrails for Kotlin (.kt/.kts) and TypeScript/React (.ts/.tsx) when touched files are part of the change.

Quick Start

Run a comprehensive review on the touched changes, applying Kotlin (.kt/.kts) and TypeScript/React (.ts/.tsx) guardrails as needed.

Frequently Asked Questions about reviewing-code

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

FAQPage Schema
How do I perform a comprehensive code review covering security and design patterns?

A comprehensive code review covering security and design patterns evaluates code quality, vulnerabilities, SOLID adherence, and performance across touched files, applying language-specific guardrails for Kotlin (.kt/.kts) and TypeScript/React (.ts/.tsx) to provide prioritized, actionable recommendations.

What's the best way to automate code quality checks before committing TypeScript changes?

Automating code quality checks before committing TypeScript changes involves running structured evaluations on .ts and .tsx files that flag readability issues, security vulnerabilities, and technical debt, categorizing issues from CRITICAL to LOW with actionable guidance to improve maintainability.

Does this code review process work with Kotlin files?

Yes, the code review process works with Kotlin files, automatically loading language-specific guardrails for .kt and .kts extensions when those touched files are part of the change, ensuring evaluations align with Kotlin development standards.

Can I use automated code reviews to assess technical debt and intent alignment?

You can use automated code reviews to assess technical debt and intent alignment by running structured evaluations across six focus areas, including quality, performance, and design, which guide reviewers with prioritized issue categorization and actionable recommendations.

When should I run a comprehensive code review on my feature implementation?

You should run a comprehensive code review on your feature implementation after implementing features or bug fixes, before commits, or when reviewing diffs, ensuring changes meet quality standards across security, performance, and maintainability before merging.

How does automated code review handle error handling and input validation vulnerabilities?

Automated code review handles error handling and input validation vulnerabilities by highlighting security risks and architectural inconsistencies, providing structured methodology that categorizes these issues by severity and offers actionable guidance to improve code safety and design.