config-validator
Validate AIWG configuration files and project setup for correctness and completeness. Use when relevant to the task.
Découvrez les skills development automation tools, comparez leurs dépôts et consultez leurs instructions.
Validate AIWG configuration files and project setup for correctness and completeness. Use when relevant to the task.
Analyze test coverage, identify gaps, and recommend test improvements. Use when relevant to the task.
Check code style compliance. Use when asked to validate code style, check naming conventions, review comments quality, or ensure file naming follows conventions. Works on whole codebase or specific changes (bra...
Review code changes for quality, correctness, and best practices. Use when asked to review a PR, review changes, or assess code quality before merge.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoid...
Overview of the `mach` compiler repository, build lifecycle, dependency rules, and workspace guidance for contributors.
Improves code structure while preserving behavior through test verification. Use when cleaning up code, reducing duplication, simplifying complexity, or reorganizing modules.
Use when managing blueprints directory structure and avoiding duplication. Always search_blueprints before creating to prevent duplicate documentation. Handles naming conventions and cross-references.
Use when managing environment variables and project settings with Mise. Covers env configuration, direnv replacement, and per-directory settings.
Use when modifying existing files, refactoring, improving code quality, or touching legacy code by applying the Boy Scout Rule to leave code better than you found it.
Use when creating or modifying GitHub Actions workflow files. Provides guidance on workflow syntax, triggers, jobs, steps, and expressions for creating valid GitHub Actions workflows that can be tested locally...
Use when setting up monorepo tooling, optimizing builds, or migrating between tools with Turborepo, Nx, Bazel, Lerna for efficient task running, caching, and code generation.
Use when configuring GitLab CI/CD pipelines, defining stages, or setting up workflow rules. Covers pipeline structure, stage ordering, and execution flow.
Use when modifying, removing, or refactoring code that lacks test coverage. Emphasizes the danger of untested changes and the RGR workflow to add characterization tests before modifications.
Use when ruboCop CI integration including GitHub Actions, plugins, and performance optimization.
Use after modifying existing systems to update blueprint documentation. Read blueprints with read_blueprint before changes, update with write_blueprint after. Prevents documentation drift.
Use when integrating Ameba into development workflows including CI/CD pipelines, pre-commit hooks, GitHub Actions, and automated code review processes.
Use when bundling JavaScript/TypeScript code with Bun's fast bundler. Covers building for different targets, tree-shaking, code splitting, and optimization strategies.
Use when optimizing GitLab CI/CD pipelines for performance, reliability, or maintainability. Covers pipeline optimization and organizational patterns.
Use when multiple fix attempts fail and you need to systematically restore to a working baseline and reimplement instead of fixing broken code.
Use when defining GitLab CI jobs, configuring scripts, setting up environments, or managing job dependencies. Covers job structure and execution options.
Automated code quality checks before commits. Use before committing code, when finishing a feature, or when user mentions "ready to commit" or "quality check".
Automatically discover formal methods and verification skills when working with formal methods. Activates for formal development tasks.
Automatically discover programming language theory skills when working with compilers. Activates for plt development tasks.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.