code-reviewer

Audit TypeScript codebases for typing discipline and anti-patterns.

Updated Aug 23, 2026

Search Tags:#typescript #refactoring #static-analysis #lint #code-review #codestyle

Ready to run

npx skills add https://github.com/phishkatlabs/phishkat-crew --skill code-reviewer-phishkatlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/phishkatlabs/phishkat-crew/tree/main/code-reviewer
Command: npx skills add https://github.com/phishkatlabs/phishkat-crew --skill code-reviewer-phishkatlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams maintain high-code quality by auditing TypeScript code for typing discipline, anti-patterns, and maintainability gaps, ensuring the next developer can understand and extend the project with confidence.

Core Features & Use Cases

Static analysis that flags missing or loose types, explicit any usage, and unsafe patterns.
Enforces consistent error handling, naming, and function responsibilities to improve readability and maintainability.
Use Case: during PR reviews, onboarding new engineers, and auditing legacy codebases to prepare for refactors and migrations.

Quick Start

Review the repository’s TypeScript codebase for readability and type-safety issues and return a prioritized remediation plan.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema

How do I automate TypeScript code review for missing types and anti-patterns?▼

Automating TypeScript code review involves running static analysis to flag missing types, loose types, explicit any usage, and unsafe patterns. This process enforces typing discipline and highlights maintainability gaps in your codebase.

What is the best way to audit a legacy TypeScript codebase before refactoring?▼

Auditing a legacy TypeScript codebase requires static analysis to identify anti-patterns, typing discipline issues, and maintainability gaps. This generates a prioritized remediation plan to reduce technical debt and prepare for refactoring.

Can I use static analysis to enforce consistent error handling and naming in TypeScript?▼

Yes, static analysis can enforce consistent error handling, naming conventions, and function responsibilities in TypeScript. Custom rule definitions identify deviations to improve readability and maintainability across the project.

Do I need a TypeScript parser to review code for type safety issues?▼

Yes, reviewing code for type safety requires a static-analysis capability or TypeScript parser along with custom rule definitions. These tools parse the codebase to detect explicit any usage and unsafe coding patterns.

How do I check TypeScript pull requests for readability and type-safety issues?▼

Checking TypeScript pull requests for readability and type-safety issues uses automated static analysis to flag missing types and unsafe patterns. This ensures typing discipline is maintained before merging changes into the main codebase.

When should I not use automated static analysis for TypeScript code review?▼

Automated static analysis for TypeScript may be less effective for rapidly prototyped code where strict typing is intentionally relaxed. It is best suited for production codebases, PR reviews, and onboarding scenarios where maintainability is critical.