static-analysis
Perform automated static code analysis on modified files. Triggers automatically after code changes to catch common issues before QA Lead review. Checks for: code complexity, dead code, type errors, import issu...
Discover databases code quality skills, compare source repositories and read the instructions for each workflow.
Perform automated static code analysis on modified files. Triggers automatically after code changes to catch common issues before QA Lead review. Checks for: code complexity, dead code, type errors, import issu...
Guide for ensuring CLI and VSCode extension produce identical analysis results. Use when verifying CLI-Extension parity, debugging output differences, or setting up consistency checks.
Create validation logic for F# backends with error accumulation and async validation. Use when: "add validation", "validate X", "input validation", "complex validation", "business rules", "check email", "requir...
Reviewt Code-Implementierungen nach Wartbarkeit, Architektur, Lesbarkeit (DDD) und sinnvoller Testabdeckung. Aktiviere bei Ticket-Abschluss, Code-Review-Anfragen, oder wenn der User nach Qualitaetspruefung frag...
Provides code quality standards for frontend applications. This skill should be used when configuring linting rules, organizing file structures, or ensuring consistency across React applications.
Provides general code quality and best practices guidance applicable across languages and frameworks. Focuses on linting, testing, and type safety.
Provides code quality standards for frontend applications. This skill should be used when configuring linting rules, organizing file structures, or ensuring consistency across React applications.
Run full project validation - Java tests, UI tests, lint, and typecheck. Comprehensive validation before commits or PRs. Use when you need to verify all code quality checks pass.
Validate the full project build (Java + TypeScript UI). Detects compilation errors, test failures, and build warnings. Use when making code changes and need to verify everything compiles.
Comment quality review. Detects LLM generation traces, implementation history, conversational tone, HOW vs WHY patterns, and redundant comments.
Generic code review for production code. Use as part of parallel code review execution.
Generic code review for test code. Use as part of parallel test review execution.
Reviews Burn deep learning code for idiomatic patterns, performance, backend portability, and best practices. Use when asked for code review, refactoring suggestions, or "is this idiomatic".
Detect and fix violations of project instructions defined in .claude/rules/. Use when checking code compliance, reviewing changes, or when the user asks about instruction violations.
Run configuration handling for persistent command configuration storage
Java code maintenance standards including prioritization, refactoring triggers, and compliance verification
Standards for identifying, prioritizing, and verifying JavaScript code maintenance and refactoring work
General documentation standards for README, AsciiDoc, and technical documentation with validation, formatting, link verification, and content review workflows
Core JavaScript development standards covering ES modules, modern patterns, code quality, async programming, and tooling
ESLint, Prettier, and StyleLint configuration standards for JavaScript code quality and formatting, including flat config setup, rule management, and build integration
Runs local validation operations for any project. Auto-detects language/framework and runs linting, type checking, tests, and dead code detection. Use this when the user says "validate", "run validation", "chec...
Reviews code for security vulnerabilities, identifies security issues, suggests improvements
Analyzes codebase, searches documentation, investigates dependencies and architecture patterns
Use when creating git commits to ensure commit messages follow project standards. Applies the 7 rules for great commit messages with focus on conciseness and imperative mood.
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.