review-code

Analyze project files with ESLint, Prettier, and TypeScript compiler.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/darenhart/zataka-ts --skill review-code-darenhart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/darenhart/zataka-ts/tree/main/.claude/skills/review-code
Command: npx skills add https://github.com/darenhart/zataka-ts --skill review-code-darenhart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires eslint, prettier, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying code quality issues, enforcing best practices, and ensuring code consistency across the project, reducing bugs and improving maintainability.

Core Features & Use Cases

  • Static Code Analysis: Detects potential bugs, code smells, and stylistic inconsistencies.
  • Linting & Formatting: Enforces coding standards using ESLint and Prettier.
  • Best Practices Verification: Checks for common anti-patterns and security vulnerabilities.
  • Use Case: After developing a new feature, run this Skill to automatically scan all new and modified files for errors and style violations before committing, ensuring a clean codebase.

Quick Start

Run a full code review on the entire project, automatically fixing any formatting issues.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I run static code analysis and linting on TypeScript project files?

Run static code analysis and linting by executing this Skill to scan project files using ESLint, Prettier, and the TypeScript compiler. It automatically identifies code smells, potential bugs, and formatting inconsistencies.

Does this code review tool check for best practices and anti-patterns?

Yes, this code review tool verifies best practices by checking for common anti-patterns and security vulnerabilities. It validates adherence to project coding standards and highlights areas for improvement.

Can I use ESLint and Prettier to automatically fix formatting issues before committing?

Yes, you can use ESLint and Prettier to automatically fix formatting issues. Run a full code review on the project to automatically scan modified files, resolve style violations, and ensure a clean codebase.

What's the best way to enforce coding standards and consistency across a project?

The best way to enforce coding standards is through automated static analysis. This Skill uses ESLint, Prettier, and TypeScript checks to detect stylistic inconsistencies, ensuring code consistency and improving maintainability.

Do I need ESLint and Prettier installed to perform best practices verification?

Yes, you need ESLint and Prettier installed as dependencies to perform best practices verification. The Skill relies on these tools alongside the TypeScript compiler to execute automated checks on project files.

Why does static analysis report code smells in my modified project files?

Static analysis reports code smells in modified project files because it detects deviations from established coding standards. The Skill uses ESLint and Prettier to identify potential bugs and stylistic inconsistencies for you to review.