quality-gate

Automate pre-PR quality checks for HTML, links, responsiveness, accessibility, and commit conventions.

Updated Apr 30, 2025
One-click install
npx skills add https://github.com/a-tabiji/atima-lp --skill quality-gate-a-tabiji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/a-tabiji/atima-lp/tree/main/.claude/skills/quality-gate
Command: npx skills add https://github.com/a-tabiji/atima-lp --skill quality-gate-a-tabiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-PR quality gates reduce back-and-forth by validating HTML syntax, links, responsiveness, accessibility, commit conventions, and diff checks before PR creation.

Core Features & Use Cases

  • HTML validation, link verification, responsive checks, and accessibility audits on changed files only.
  • Commit-convention enforcement to ensure messages follow the standard format.
  • Diff analysis to surface unintended file changes prior to PR submission.

Quick Start

Run the pre-PR quality gate to ensure all checks PASS or WARN before PR creation.

Frequently Asked Questions about quality-gate

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

FAQPage Schema
How do I automate accessibility and HTML validation checks before creating a pull request?

Automated pre-PR quality checks validate HTML syntax, accessibility, and link integrity on modified files to ensure code meets standards before pull request creation.

What is the best way to enforce commit message conventions during pre-PR checks?

Commit-convention enforcement validates modified commit messages against standard formats during pre-PR quality checks, ensuring all messages follow the required convention before submission.

Can I run responsive design validation on only the files changed in my repository?

Responsive validation runs exclusively on changed files, applying diff analysis to surface unintended modifications and verify responsive design prior to pull request creation.

Does link verification work automatically as part of pre-PR quality gates?

Link verification operates automatically as a pre-PR quality gate, checking link integrity on modified files to ensure all links are valid before pull request submission.

Why use diff analysis for pre-PR quality checks instead of validating the entire repository?

Diff analysis targets only modified files, surfacing unintended changes and validating HTML, links, responsiveness, and accessibility efficiently before pull request creation.