code-review

Enforce TypeScript type safety and FSD architecture conformance in ChordLens code reviews.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ChordLens Code Review provides a structured guide to assess and enforce code quality standards, focusing on TypeScript type safety, adherence to the Feature-Sliced Design (FSD) architecture, robust API error handling, and coding conventions during BE-FE boundary checks.

Core Features & Use Cases

  • Enforces TypeScript type safety by avoiding any and ensuring explicit interfaces.
  • Enforces FSD architecture conformance with proper layer imports and placement.
  • Provides API error handling guidelines for 400/500/504 responses and consistent error shapes.
  • Enforces coding conventions: no console.log, no unnecessary useEffect for data fetching, and incentives for named exports.
  • Supports BE-FE boundary cross-checks by aligning FE models with BE schemas.

Quick Start

Run the verification workflow to check TypeScript types, FSD architecture, and lint rules for your codebase.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce Feature-Sliced Design architecture in a TypeScript project?

Enforce Feature-Sliced Design (FSD) architecture by validating proper layer imports and module placement during code reviews. This Skill checks TypeScript projects for architectural conformance, ensuring layers do not violate FSD boundary rules and structural standards are met.

What is the best way to handle API error handling and BE-FE boundary checks?

Handle API error handling by aligning frontend models with backend schemas for BE-FE boundary cross-checks. This Skill provides guidelines for 400, 500, and 504 API responses, ensuring your TypeScript frontend maintains consistent error shapes and type safety.

How do I check TypeScript type safety and avoid any in my codebase?

Check TypeScript type safety by enforcing explicit interfaces and avoiding the any type during static type checks. This Skill verifies that your codebase adheres to strict typing conventions, ensuring robust type safety across frontend and backend boundaries.

Does this code review workflow check for unnecessary useEffect and console statements?

Yes, this code review workflow checks for unnecessary useEffect statements used for data fetching and enforces coding conventions by flagging console.log outputs. It verifies style conformance and incentivizes named exports to maintain clean code standards.

Can I use this Skill for static type checking and lint rules verification in ChordLens?

Yes, you can use this Skill for static type checking and lint rules verification in ChordLens TypeScript projects. It runs a verification workflow that checks TypeScript types, FSD architecture layer validations, and lint conformance with clear verification outcomes.