justfile-style
Style guidelines for justfile recipe documentation. Use when writing or editing justfiles to ensure consistent and concise documentation.
Discover databases code quality skills, compare source repositories and read the instructions for each workflow.
Style guidelines for justfile recipe documentation. Use when writing or editing justfiles to ensure consistent and concise documentation.
Code quality guidelines. ALWAYS use skill for ANY code changes.
PHP 8.5+ modern patterns, PSR standards, and SOLID principles. Use when reviewing PHP code, checking type safety, auditing code quality, or ensuring PHP best practices. Triggers on "review PHP", "check PHP code...
Apply Rules Repository conventions and forward-only workflow. Use when generating or editing docs, prompts, or code in projects that consume this repository or when this repository is the active workspace. Ensu...
PolicyEngine code review patterns - validation checklist, common issues, review standards
PolicyEngine coding standards, formatters, CI requirements, and development best practices
멀티 AI 코드 리뷰 오케스트레이터. Claude, Codex, Gemini, Droid를 조율하여 종합적 코드 리뷰 수행. "멀티 AI 리뷰", "코드 리뷰", "종합 리뷰" 요청 시 활성화됩니다.
PR 리뷰 대기 및 자동 수정 루프. "리뷰 대기", "리뷰 반영 대기", "자동 리뷰 수정", "review loop" 요청 시 활성화됩니다.
C# code style and naming conventions based on POCU standards. Covers naming rules (mPascalCase for private, bBoolean prefix, EEnum prefix), code organization, C# 9.0 patterns. Use PROACTIVELY for C# code review...
OpenAI Codex CLI fundamentals for code analysis, review, and validation. Use when (1) executing codex commands for code review/analysis, (2) configuring models (gpt-5.2-codex/gpt-5.2/gpt-5.1-codex-max/codex-min...
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
TypeScript best practices, strict typing patterns, and type safety strategies. Use when implementing TypeScript code with focus on type correctness and maintainability.
Production-ready safety checklists for Rails implementation. Covers nil safety, ActiveRecord patterns, security vulnerabilities, error handling, and performance. Use before marking any file complete during impl...
Comprehensive code quality validation using Solargraph, Sorbet, and Rubocop for A+ Rails code. Trigger keywords: quality gates, validation, solargraph, sorbet, rubocop, type checking, linting, code quality, sta...
Enforces modern Python 3.11+ coding standards, PEP 8 compliance, and type-hinting best practices automatically. This skill should be used when writing, reviewing, or refactoring Python code to ensure consistenc...
Write clean, error-free markdown that IDEs and linters can parse without warnings. Use when writing documentation, README files, or skill files with code examples.
Multi-language code quality standards for TypeScript, Python, Go, and Rust. Enforces type safety, security, performance, and maintainability with progressive enforcement. Use when writing, reviewing, or refacto...
Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
Synchronizes tsconfig.json paths from package.json imports field. Ensures TypeScript resolves subpath imports (#imports) correctly during development.
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.