final-quality-check

Orchestrate CI/CD pipelines, E2E testing, and design-system compliance gates.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/steve-piece/bytheslice --skill final-quality-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: final-quality-check
Source: https://github.com/steve-piece/bytheslice/tree/main/skills/final-quality-check
Command: npx skills add https://github.com/steve-piece/bytheslice --skill final-quality-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires husky, eslint-plugin-tailwindcss, stylelint, stylelint-config-standard, @playwright/test, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the inconsistency and manual overhead of setting up production-grade quality infrastructure by orchestrating a standardized, multi-stage CI/CD and verification baseline.

Core Features & Use Cases

  • Automated Scaffolding: Dispatches specialized agents to configure CI/CD workflows, E2E testing, and design-system compliance gates.
  • Verification Baseline: Enforces local pre-push hooks and branch protection to ensure code quality before it reaches the repository.
  • Use Case: When starting a new project or upgrading an existing one, use this Skill to instantly bootstrap a professional-grade pipeline that includes Playwright E2E tests, linting, and visual regression checks.

Quick Start

Run the final-quality-check skill to automatically scaffold the complete CI/CD and E2E testing baseline for this project.

Frequently Asked Questions about final-quality-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate CI/CD pipelines and E2E testing setup for a new project?

Automating CI/CD pipelines and E2E testing involves scaffolding standardized workflows, configuring Playwright tests, and enforcing local pre-push hooks to ensure code quality before repository integration. This skill orchestrates that multi-stage baseline automatically.

What is the best way to enforce design-system compliance and quality gates in GitHub Actions?

Enforcing design-system compliance in GitHub Actions requires automated linting gates using stylelint and eslint-plugin-tailwindcss. This skill dispatches specialized agents to configure these verification workflows alongside branch protection rules.

Do I need the GitHub CLI installed to automate branch protection and verification workflows?

Yes, you need the GitHub CLI installed and a configured package manager to execute multi-stage scaffolding for branch protection and automated verification workflows. These dependencies are required to orchestrate the complete quality assurance baseline.

How does automated E2E testing with Playwright integrate into a CI/CD pipeline?

Automated E2E testing with Playwright integrates into CI/CD pipelines through multi-stage scaffolding that configures test execution workflows. The skill sets up these tests alongside local pre-push hooks using husky to verify code before it reaches the repository.

Can I upgrade an existing repository with automated quality assurance and visual regression checks?

Yes, you can upgrade existing repositories by bootstrapping a professional-grade pipeline that includes Playwright E2E tests, stylelint visual regression checks, and automated verification workflows. The skill applies standardized quality infrastructure to both new and existing projects.

What limitations should I consider when scaffolding quality gates with husky and stylelint?

Limitations when scaffolding quality gates include requiring a pre-configured package manager and GitHub CLI for multi-stage execution. The standardized baseline assumes compatibility with husky pre-push hooks and stylelint-config-standard for design-system compliance enforcement.