Run comprehensive Elixir quality checks (format, credo, dialyzer, tests) with proper error handling and reporting. Use when validating code quality, before commits, or preparing for deployment.
Skill for verifying overall codebase quality. Covers architecture consistency, convention compliance, and potential issue detection. Triggers: code review, architecture review, quality check, refactoring, 코드 리뷰, コードレビュー, 代码审查
Core rules for bkit plugin. PDCA methodology, level detection, agent auto-triggering, and code quality standards. These rules are automatically applied to ensure consistent AI-native development. Triggers: bkit, PDCA, 개발, develop, implement, 기능, feature, 버그, bug, 코드, code, 설계, design, 문서, document
Synchronizes tsconfig.json paths from package.json imports field. Ensures TypeScript resolves subpath imports (#imports) correctly during development.
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
Performs comprehensive code reviews for Python files following PEP 8 and Google Python Style Guide standards. Checks code quality, best practices, security, performance, maintainability, and style compliance. Use when reviewing Python code or when asked to check, audit, or improve Python code quality.
TypeScript strict mode patterns. Use when writing any TypeScript code.
プロジェクトの開発ルール遵守をチェックし、違反を報告・修正する。TypeScriptでのany禁止、CI品質チェック必須、ローカル動作確認、conventional commit採用、依存バージョン固定、ユニットテスト必須、コミット前lint/format/test実行のルールを適用。コード作成・編集後、コミット前、PRレビュー時に使用。`/dev-standards`で明示的にチェック、`--fix`で自動修正を実行。
Use when setting up project-specific hooks for Claude Code enforcement. Load during INIT state when .claude/hooks/ is missing, or when creating new project. Installs 5 hooks that read from .claude/config/project.json (tests, health, dependencies).
Detect and resolve incoherence in documentation, code, specs vs implementation. Includes reconciliation phase for applying user-provided resolutions.
Skill for defining coding rules and conventions. Ensures consistent code style and specifies coding standards for AI collaboration. Triggers: convention, coding style, naming rules, 컨벤션, コンベンション, 编码风格
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 consistency with PEP 8, proper type hints, Google-style docstrings, and modern Python idioms.
Enforce mandatory npm test and npm run lint execution after every code change with no exceptions for code quality and test coverage compliance
TypeScript language rules with strict mode, testing, linting, and CI/CD best practices
Run formatting, lint, typecheck, and tests for this repo; use when validating changes or investigating CI failures.
Reviews code for quality, security, and maintainability. Use after implementing features, completing significant work, or when user asks for code review.
Use when creating or editing any bash script (.sh) - ensures shellcheck passes after every edit with zero warnings
Breaking change detection patterns and dependency safety analysis for PR reviews
Principle of Least Astonishment (POLA) - ensure code changes behave as users and developers expect. Activate when making code changes, refactoring, modifying APIs, renaming functions/variables, changing file structure, or reviewing proposed implementations. Guides predictable, convention-following changes.
Enforce semantic CSS variable theming in Tailwind projects. Prevents raw colors (hex, rgb) and non-theme Tailwind classes. Use when project has semantic tokens, CSS vars, or custom ESLint theming rules.
Use AFTER any code changes (feature implementation, bug fix, refactor) to enforce mandatory dual-pass review. First pass reviews unstaged changes for correctness and convention compliance. Second pass ONLY executes if first pass made any corrections. Ensures work follows project conventions, development rules, and best practices before task completion.
Audits the project for consistency issues that may arise from manual editing. Checks package scripts, tsconfig paths, README tables, and other conventions.
