ci

Run Prettier, ESLint, TypeScript checks, and Vitest tests with aggregated reports.

1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/kasiopeiya/oidc-learning-sandbox --skill ci-kasiopeiya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/kasiopeiya/oidc-learning-sandbox/tree/main/.claude/skills/ci
Command: npx skills add https://github.com/kasiopeiya/oidc-learning-sandbox --skill ci-kasiopeiya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to run static analysis and unit tests across backend and frontend locally, mirroring a CI pipeline to catch issues early before deployment.

Core Features & Use Cases

  • Prettier formatting checks across the repository to enforce consistent styling.
  • ESLint static analysis for backend and frontend to catch code quality issues.
  • TypeScript type checks for both backend and frontend to ensure type safety.
  • Unit tests execution (Vitest) for backend and frontend to validate functionality.
  • Detailed, aggregated reports highlighting failures and suggested fixes.

Quick Start

Run the /ci command at the repository root to execute the full CI pipeline locally.

Frequently Asked Questions about ci

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

FAQPage Schema
How do I run a local CI pipeline to check TypeScript types and Vitest tests before deployment?

You can run local CI checks by executing a single command at the repository root to automate Prettier formatting, ESLint linting, TypeScript type checks, and Vitest tests across backend and frontend, producing an aggregated report.

What is the best way to run Prettier formatting and ESLint static analysis across a full-stack repository?

The best way to run Prettier and ESLint across a full-stack repository is to simulate a CI workflow that orchestrates formatting checks and static analysis for both backend and frontend, catching code quality issues early before deployment.

Can I use this local CI workflow to validate code quality on pull requests?

Yes, this local CI workflow supports PR validation by running formatting checks, linting, type checks, and tests across backend and frontend to verify code quality before merging or deploying changes.

Does this CI simulation require any external dependencies or components to run?

No, this CI simulation requires no external dependencies or components to run static analysis and unit tests locally, relying entirely on your existing repository configurations for Prettier, ESLint, TypeScript, and Vitest.

How do I get a structured report of TypeScript type check and Vitest test failures?

You get a detailed, structured report of TypeScript type check and Vitest test failures by running the full CI pipeline simulation, which aggregates results across backend and frontend and highlights failures alongside suggested fixes.

When do I need to run static analysis and unit tests locally instead of relying on remote CI?

You need to run static analysis and unit tests locally when you want to mirror a CI pipeline to catch issues early before deployment, ensuring formatting, linting, type safety, and functionality pass within your development environment.