Loading...
Loading...
Found 51 Skills
Execute a micro-level Flutter code quality audit. Validates code against live GitHub standards for testing, architecture, and code implementation. Produces a detailed violations report with prioritized action plan. Use when the user asks to check Flutter code quality, validate best practices, or review code standards compliance. Triggers on: 'flutter best practices', 'code quality', 'code review', 'flutter standards', 'architecture compliance', 'testing quality'.
Run shellcheck and actionlint on shell scripts and GitHub Actions workflows. Use before pushing or when fixing lint issues.
[DevOps & Infra] Run linters and fix issues for backend or frontend
Review checks reference for validating Umbraco backoffice extensions
Use this skill when posting the final summary comment after all inline comments are posted. Apply as the LAST step of code review after all findings are classified and inline comments are complete. Detects context (GitHub sticky comment, new comment, or local file) and routes output accordingly.
Audit claude-skills repository documentation with systematic 9-phase review: standards compliance, official docs verification via Context7/WebFetch, code examples accuracy, cross-file consistency, and version drift detection. Auto-fixes unambiguous issues with severity classification. Use when: investigating skill issues, major package updates detected (e.g., v1.x → v2.x), skill not verified >90 days, before marketplace submission, or troubleshooting outdated API patterns, contradictory examples, broken links, version drift.
Scans code against 17 named design smells and produces a structured diagnostic report. Use when reviewing a PR for design quality, evaluating unfamiliar code against a comprehensive checklist or when the user asks for a red flags scan. Not for diagnosing why code feels complex (use complexity-recognition) or evaluating whether a PR maintains design trajectory (use code-evolution).
Run after making Docyrus API changes to catch bugs, performance issues, and code quality problems. Use when implementing or modifying code that uses Docyrus collection hooks (.list, .get, .create, .update, .delete), direct RestApiClient calls, query payloads with filters/calculations/formulas/childQueries/pivots, or TanStack Query integration with Docyrus data sources. Triggers on tasks involving Docyrus API logic, data fetching, mutations, or query payload construction.
Review RTK Rust code for idiomatic simplification. Detects over-engineering, unnecessary allocations, verbose patterns. Applies Rust idioms without changing behavior.
Vue2 Frontend Code Review Assistant. Reviews code changes in the src directory of Vue2 projects. Covers 9 major dimensions: component specifications, code style, naming, logic, network requests, computed, security, best practices, and absolute prohibitions. Trigger scenarios: pre-merge review, pre-commit quality check, Code Review for Vue2 code.
This skill should be used when the user requests "commit", "git commit", "create commit", or wants to commit staged/unstaged changes following conventional commits format
[Testing] Autonomous subagent variant of code-review. Use when reviewing code changes, pull requests, or performing refactoring analysis with focus on patterns, security, and performance.