Total 43,450 skills, Code Quality has 2026 skills
Showing 12 of 2026 skills
Configures Husky, lint-staged, commitlint, and Python pre-commit
Audit code comments and docstrings quality across 6 categories (WHY-not-WHAT, Density, Forbidden Content, Docstrings, Actuality, Legacy). Use when code needs comment review, after major refactoring, or as part of ln-100-documents-pipeline. Outputs Compliance Score X/10 per category + Findings + Recommended Actions.
API contract audit worker (L3). Checks layer leakage in method signatures, missing DTOs, entity leakage to API, inconsistent error contracts, redundant method overloads. Returns findings with 4-score model (compliance, completeness, quality, implementation).
Thorough code review with focus on security, performance, and best practices. Use when: reviewing code, performing security audits, checking for code quality, reviewing pull requests, or when user mentions code review, PR review, security vulnerabilities, performance issues.
Julia development guidelines covering multiple dispatch, type system, performance optimization, and scientific computing best practices.
Review Encore Go code for best practices.
Guidelines for implementing Clean Architecture patterns in Flutter and Go applications, with emphasis on separation of concerns, dependency rules, and testability.
Debug experiment code with structured error analysis. Categorize errors, apply targeted fixes with retry logic, and use reflection to prevent recurring issues. Use when experiment code fails or produces incorrect results.
Apex code quality guardrails for Salesforce development. Enforces bulk-safety rules (no SOQL/DML in loops), sharing model requirements, CRUD/FLS security, SOQL injection prevention, PNB test coverage (Positive / Negative / Bulk), and modern Apex idioms. Use this skill when reviewing or generating Apex classes, trigger handlers, batch jobs, or test classes to catch governor limit risks, security gaps, and quality issues before deployment.
Run a full Dune app platform review against a React/TypeScript CDF codebase, following the cognitedata/dune-app-reviews scoring criteria. Produces three artifacts: review-files.md (per-file inventory), review-packages.md (dependency audit), and review-report.md (scored report with must/should/nice-fix items). Use when the user asks for a Dune app review, pre-submit review, approval review, app certification review, code quality audit, CDF platform review, or "run dune-review" on a codebase before submission.
Organize reusable programming patterns / library usages / technical skills that answer "To do this kind of thing, the correct approach is this" into a prescriptive reference library, which can be retrieved and reused as needed during feature-design and issue-analyze phases. Three types: pattern (design patterns, programming idioms), library (usage and pitfalls of a certain library/framework), technique (specific operation skills / command recipes). Trigger scenarios: When the user says "record a trick", "this usage is worth recording", "tricks", "record library usage", or when a skill worth archiving is discovered during feature-design / issue-analyze phases and actively pushed. Refer to `codestable/reference/system-overview.md` for how to distinguish it from learning / decisions / explore.
Phase 2 of the feature workflow —— Write code according to the implementation sequence in {slug}-design.md, and submit a completion report in a unified format for user review after finishing. Prerequisites: {slug}-design.md has been approved (standard design includes test design, or fastforward design includes acceptance criteria), and {slug}-checklist.yaml exists in the same directory. Trigger scenarios: User says "The plan is confirmed, start implementation", "Write code according to the plan", "Start working". If you encounter situations not covered by the plan during implementation (new concepts, out-of-scope files, need for patch branches), proactively stop and go back to discuss the plan instead of pushing forward blindly.