skills.rest
Srajangpt1
Srajangpt1COMMUNITY
Explore all skills by this author →
GitHub

ts-style-review

Review TypeScript code against the Google TypeScript Style Guide and team conventions.

Updated Apr 12, 2026
Search Tags:#typescript#zod#imports#naming-conventions#code-review#style-guide#google-ts
One-click install
npx skills add https://github.com/Srajangpt1/dataeye --skill ts-style-review-srajangpt1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ts-style-review
Source: https://github.com/Srajangpt1/dataeye/tree/main/packages/browseros-agent/.claude/skills/ts-style-review
Command: npx skills add https://github.com/Srajangpt1/dataeye --skill ts-style-review-srajangpt1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a concise, actionable checklist to identify TypeScript style, naming, import, and type-system violations according to the Google TypeScript Style Guide and team conventions, reducing review friction and inconsistent codebases.

Core Features & Use Cases

  • Comprehensive Style Checks: Covers file structure, imports/exports, variable declarations, classes, functions, control flow, equality, and disallowed features.
  • Type & Schema Guidance: Enforces TypeScript best practices (prefer interface, use unknown over any) and team Zod schema placement and inference conventions.
  • Review & PR Use Case: Use during pull request reviews or automated code audits to call out default exports, var usage, @ts-ignore, mutable exports, and other violations before merge.

Quick Start

Run a review of the provided TypeScript file and list deviations from the Google style guide and the project's Zod schema conventions.

Frequently Asked Questions about ts-style-review

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

FAQPage Schema
How do I review TypeScript code for Google style guide violations?▼

To review TypeScript code for Google style guide violations, validate file structure, imports, naming conventions, and type usage. This process flags disallowed features like var, default exports, and @ts-ignore to ensure codebase consistency during pull requests.

What is the best way to enforce Zod schema placement in TypeScript reviews?▼

Enforcing Zod schema placement in TypeScript reviews involves checking schema definitions against team conventions for inference and structure. It validates that schemas are positioned correctly and that type usage prefers unknown over any.

Can I use a TypeScript style checker for repository-wide audits?▼

Yes, you can use a TypeScript style checker for repository-wide audits across frontend and agent code. It systematically identifies deviations in control flow, error handling, classes, and functions throughout the entire repository.

Does Google TypeScript style allow default exports and var declarations?▼

No, Google TypeScript style does not allow default exports, var declarations, @ts-ignore, or mutable exports. Reviews should actively flag these disallowed features alongside checks for private identifiers and improper type usage.

How do I check TypeScript naming conventions and imports in a pull request?▼

To check TypeScript naming conventions and imports in a pull request, validate export structures and variable declarations against the style guide. This catches inconsistencies in class definitions and function structures before merging.

Related Skills

Explore More Software Engineering Skills→
ylxaiylxai
2

zod

Guide Zod schema validation in TypeScript applications.

Community
Advanced
SouleymaneSy7SouleymaneSy7
2

docs-review

Review documentation changes for Metabase writing style guide compliance.

Community
Advanced
mymx2mymx2
4

sql-parser-cst

Parse SQL statements into a Concrete Syntax Tree preserving comments and whitespace.

Community
Advanced
einja-inceinja-inc
1

coding-standards

Enforce TypeScript/React naming conventions, import orders, and linting standards.

Official
Basic