Discover documentation automation tools skills, compare source repositories and read the instructions for each workflow.
Generates or augments minimal Vitest tests for changed/new code in Next.js + TypeScript projects. Invoked by prompt-classifier on TEST or chained from other flows. Focuses on happy path + key edges. Chains veri...
Builds and refactors code safely; prefers small diffs, clear validation steps, and testable outcomes.
Senior frontend code review for Vue/TypeScript. Use when reviewing PRs, checking code quality, or validating against project conventions.
[slop] [debug] [unused] [duplicates] [all] - Cleans up code in the current branch. Removes AI artifacts, debug statements, unused code, and duplicates. Use when preparing for PR or cleaning up after AI-assisted...
This skill should be used when the user asks to "review code", "review this PR", "code review", "audit this code", or mentions reviewing pull requests, security checks, or code quality. Covers security (OWASP),...
Runs automated verification after code changes in Next.js + TS projects. Invoked by prompt-classifier in IMPLEMENT/EDIT sequences (after write/edit). Executes lint, scoped typecheck, tests, custom assertions; r...
Reviews code for security vulnerabilities. Use when security concerns are detected or before deploying critical changes.
Reviews code for construction management applications with focus on CSI data integrity, BIM workflows, and domain-specific correctness. Use when reviewing changes to calculator logic, database schemas, or const...
Code review guidelines covering code quality, security, and best practices.
Performs static analysis, security scanning, and code linting. Use to detect bugs, API key leaks, and anti-patterns before committing.
Review code implementations for quality, security, and architectural soundness. Use when reviewing code changes, PRs, or implementations. Conducts John Carmack-level review examining correctness, simplicity, ed...
Diagnose environment issues, identify missing dependencies, and provide fix instructions
Enforces documentation standards and structure for this project. This skill should be used when creating, updating, or organizing documentation to ensure compliance with project rules, prevent redundancy, and m...
Comprehensive TypeScript development guidance covering configuration, type safety, architectural patterns, and best practices. Use when working with TypeScript codebases for (1) TypeScript configuration and set...
Create consistent, high-quality educational programming exercises or tutorials following strict template guidelines. Use this skill whenever you need to create or refine a programming exercise or tutorial for y...
Use for ALL code changes - new features, bug fixes, refactoring. Write the test first, watch it fail, then write minimal code to pass.
Shared utilities for file deprecation, directory structure creation, TODO file updates, workflow lifecycle management, archive management, and VCS abstraction (GitHub/Azure DevOps PR feedback methods). Used by...
Create the deliverable (code, documentation, tests, content) following the user's standards and best practices. Use after validation passes to actually build the work product.
ユーザーがコードレビューを依頼したとき、またはコードの可読性・保守性・命名規則・コメントの改善提案を求めたときに使用します。指定されたファイルに対してテンプレートに基づく一貫したコードレビューを自動生成します。...
Validate game data files against sources and cross-reference checks. Use to verify data accuracy, find inconsistencies, and ensure data integrity across all JSON files.
Nx monorepo management skill for AI-native development. This skill should be used when working with Nx workspaces, project graphs, affected detection, code generation, and caching. Use when: analyzing dependenc...
TypeScript safety gate + drift control (no new any/as any/non-null assertions). Triggers on "TS:" prefix and TypeScript safety work.
Use when about to fix code, modify implementation, or address errors. MUST read before saying "修正します", "fix", "修正する", "直す", "対処する". Prevents symptom-driven fixes.
Use when implementing any feature or bugfix, before writing implementation code
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.