review-perspective-selector

Select review perspective decks for TypeScript files using path-based rules.

Updated Nov 26, 2025
One-click install
npx skills add https://github.com/shiroinock/Darts-Score-Trainer --skill review-perspective-selector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-perspective-selector
Source: https://github.com/shiroinock/Darts-Score-Trainer/tree/main/.claude/skills/review-perspective-selector
Command: npx skills add https://github.com/shiroinock/Darts-Score-Trainer --skill review-perspective-selector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically selects an appropriate review perspective deck based on the type of implementation file, saving you time in code reviews and ensuring comprehensive coverage.

Core Features & Use Cases

  • Automated perspective selection: Detects file type (domain logic, UI, utilities, tests) and selects matching review points.
  • Context-aware prompts: Generates a list of perspective files to feed to review-file agent.
  • Use Case: When reviewing a new module such as src/utils/gameLogic.ts, it suggests the perspectives to check (e.g., typescript.md, specification.md).

Quick Start

Use the review-perspective-selector skill to determine appropriate review perspectives for a given file path, e.g. "src/utils/gameLogic.ts". The skill will output a list of perspective files, such as:

  • .claude/review-points/typescript.md
  • .claude/review-points/specification.md

Frequently Asked Questions about review-perspective-selector

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

FAQPage Schema
How do I automate code review perspective selection for TypeScript files?

Automated perspective selection detects your file type—domain logic, UI, utilities, or tests—and matches it to relevant review checklists. review-perspective-selector analyzes the file path and outputs a deduplicated list of perspective files like typescript.md, specification.md, or test-quality.md to feed into your review workflow.

What review perspectives should I use for different file types?

Path-based rules assign perspectives by domain: domain logic files get specification.md, coordinate calculations get coordinates.md, UI components get appropriate UI perspectives, state stores get state-management perspectives, type definitions get typescript.md, and test files get test-quality.md. The Skill automates this assignment.

Can I use this Skill to standardize code reviews across my TypeScript project?

Yes. The Skill standardizes reviews by automatically selecting consistent perspective decks based on file classification across your codebase. This ensures comprehensive coverage and reduces manual perspective selection for domain logic, utilities, components, types, and tests.

How does the Skill handle files that fit multiple review perspectives?

The Skill outputs a deduplicated set of perspective identifiers, eliminating overlaps when a file matches multiple categories. This produces a clean, non-redundant list of review points to apply.

What input do I need to provide to get perspective recommendations?

Provide the file path—such as src/utils/gameLogic.ts or src/components/Button.tsx—and the Skill applies its classification rules to determine which perspective files apply to that file type.

Does this Skill work with existing code review workflows?

Yes. The Skill integrates with review-file agent by generating the perspective deck list that agent consumes. It sits upstream in your review pipeline, automating the selection step before deeper analysis begins.