How does it handle code formatting?

It runs formatting commands only when necessary, specifically targeting changed files to minimize unnecessary formatting churn in your repository.

What happens if an E2E test fails?

The skill provides a summary of the failure and suggests switching to the e2e-playwright skill for deep-dive debugging using traces and screenshots.

When should I use this skill?

Use it whenever you need to verify your changes, run CI checks, or perform a final quality check before committing code or pushing to production.

Does it support multiple browsers?

Yes, it specifically handles builds and checks for both Chrome and Firefox, which is particularly useful for browser extension development.

What does the Quality Gates skill do?

It automates the process of running linting, type-checking, building projects, and executing E2E tests to ensure repository health and code quality.

Quality Gates

Name: Quality Gates
Author: daichan132

bydaichan132

•

Security & Testing

Automates repository quality checks including linting, multi-browser builds, and E2E testing for browser extensions.

About

The Quality Gates skill streamlines the development workflow for browser extensions by automatically managing essential code quality checks. It intelligently inspects repository changes to determine whether to run linting, type-checking, or cross-browser builds for Chrome and Firefox. By integrating End-to-End (E2E) testing via Playwright, it ensures that UI and behavioral changes are verified before deployment, providing a summarized pass/fail report and clear next steps for debugging and fixing issues.

Key Features

Automated linting and type-checking for code consistency
Intelligent E2E testing triggers based on UI or behavioral changes
Cross-browser build management for Chrome and Firefox extensions
Minimal formatting churn by targeting specific entry points
Formatted result summaries with actionable error excerpts
28 GitHub stars

Use Cases

Verifying code quality before submitting a pull request
Running regression tests after making UI changes to a web application
Automating multi-browser builds for Chrome and Firefox extension updates

About

Key Features

Automated linting and type-checking for code consistency
Intelligent E2E testing triggers based on UI or behavioral changes
Cross-browser build management for Chrome and Firefox extensions
Minimal formatting churn by targeting specific entry points
Formatted result summaries with actionable error excerpts
28 GitHub stars

Use Cases

Verifying code quality before submitting a pull request
Running regression tests after making UI changes to a web application
Automating multi-browser builds for Chrome and Firefox extension updates