Skill UI

This skill reviews generated or changed test code against universal testing rules before deployment. It prevents common failure modes like mock-heavy unit tests, near-duplicate test bodies, and tests that re-verify the framework. It enforces best practices such as testing behavior over implementation, justifying mocks at system boundaries, and ensuring every test has a clear justification. Use it when reviewing diffs, new test files, or when writing new tests to ensure high-quality, maintainable test suites.

Build end-to-end tests with TestDriver.ai, an AI code reviewer that runs every pull request in a real desktop sandbox, finds bugs, and creates regression tests for web, Electron, and native apps.

This comprehensive workflow provides a complete cycle of quality assurance for software development. It covers every stage from defining the test strategy (TDD, Unit Testing) through integration, E2E testing, browser automation, performance profiling, security scanning, and final code review. Use this when setting up robust testing infrastructure or ensuring production-ready software quality.

This skill reviews UI code for design system compliance, accessibility standards, and best practices. It checks for hardcoded values, component conventions, mobile responsiveness, performance optimization, typography consistency, and visual coherence. It ensures code aligns with established design tokens and accessibility guidelines like WCAG.

Aggregates Uncle Bob’s Clean Code, Architecture, Coder, Agile, and design-pattern guidance to evaluate reviews, refactors, and architecture decisions, and to surface professionalism heuristics without replacing your linter or formatter.

Vibers provides a human-in-the-loop code review workflow for AI-generated GitHub projects. Users push code, and the service reviews it against a specification, checks for security issues, and submits a pull request with suggested fixes. It supports various languages and requires adding a collaborator and configuring a GitHub Action to trigger the review process.

A critical skill for reviewing WooCommerce extensions, payment integrations, and checkout logic before deployment. Ensures code follows security standards, HPOS compatibility, proper data handling, and runtime discipline to prevent systematic AI failures.

A specialized tool for auditing WordPress plugins, themes, and blocks before deployment. It checks for security vulnerabilities like SQL injection, XSS, and improper escaping, ensures API correctness, and enforces internationalization standards. Use it to review generated code or perform security assessments on WordPress environments.

A five-axis code review checklist covering correctness, security, readability, performance, and test coverage to produce actionable comments instead of style nitpicks. Use for reviewing code, diffs, or pull requests.

Statically review MCP configuration files (.mcp.json, Cursor, VS Code, Claude, Windsurf) for mutable package references such as @latest, tags, or version ranges before approval or in CI, without executing discovered servers.

Runs ECC's engineering process retroactively on existing projects. Audits current state, reconstructs past decisions, and produces a four-axis gap register (thinking, coding practice, missing features, technology selection). Executes fixes forward through the plan-TDD-review pipeline. Ideal for mid-project adoption, inheriting codebases, or identifying what was missed.

This command executes a single experiment iteration for autoresearch workflows. Users review history, decide changes, edit code, commit, and evaluate results. It follows strategy escalation rules to optimize performance systematically without modifying the evaluator.