code-review

Analyze code changes for security, performance, and TypeScript issues.

Updated May 6, 2023
One-click install
npx skills add https://github.com/motoedie/.dotfiles --skill code-review-motoedie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/motoedie/.dotfiles/tree/main/ai-tools/skills/code-review
Command: npx skills add https://github.com/motoedie/.dotfiles --skill code-review-motoedie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps catch common coding errors and potential issues before they become problems in your codebase, improving code quality and security.

Core Features & Use Cases

  • Static Analysis: Analyzes code without execution to find bugs, security vulnerabilities, and performance bottlenecks.
  • Concrete Fixes: Provides specific, copy-pasteable solutions for identified issues.
  • Use Case: Before pushing your code or opening a pull request, run this Skill to ensure your changes adhere to best practices and are free from common pitfalls.

Quick Start

Review the current code changes for potential issues and suggest fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How does static code analysis find security vulnerabilities and TypeScript type errors?

Static code analysis inspects your code without execution to identify input-boundary issues, security vulnerabilities, and TypeScript correctness problems, providing concrete, copy-pasteable fixes for each detected issue.

How do I check code changes for performance bottlenecks and edge cases before a pull request?

You can analyze code changes for performance bottlenecks and edge cases before a pull request by running static analysis to pinpoint input validation gaps and robust error handling improvements alongside copy-pasteable solutions.

Can static analysis detect input validation and security issues without executing tests?

Yes, static analysis detects input validation and security issues without executing any commands or tests by reviewing the code structure directly to uncover vulnerabilities and provide specific fixes.

What is the best way to ensure TypeScript correctness and robust error handling in my codebase?

The best way to ensure TypeScript correctness and robust error handling is using static analysis to review code changes, catching type safety issues and edge cases before they enter your codebase.

Does static code analysis provide concrete fixes for edge-case issues and performance optimizations?

Static code analysis provides concrete, copy-pasteable fixes for edge-case issues and performance optimizations, directly addressing input validation, security vulnerabilities, and TypeScript type safety without running commands.

Why should I run static analysis on code changes instead of just relying on manual code review?

Running static analysis on code changes catches common coding errors, security vulnerabilities, and performance bottlenecks that manual review might miss, ensuring your changes adhere to best practices before pushing.