quality-gate

Run the full zero-tolerance quality gate on a feature branch.

Updated Jul 18, 2025
One-click install
npx skills add https://github.com/dougborg/stocktrim-openapi-client --skill quality-gate-dougborg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/dougborg/stocktrim-openapi-client/tree/main/.claude/skills/quality-gate
Command: npx skills add https://github.com/dougborg/stocktrim-openapi-client --skill quality-gate-dougborg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incomplete or shortcut-based work from being marked done by enforcing a strict, CLAUDE.md-aligned pre-done checklist covering branch hygiene, clean diffs, linting, and full test pass before success is declared.

Core Features & Use Cases

  • Full quality gate execution: Runs the repository’s complete uv run poe check pipeline (root and MCP server test suites) to ensure everything passes before proceeding.
  • Forbid known bad shortcuts: Detects and blocks adding # noqa, # type: ignore, or skipped tests, and flags prohibited edits to generated code paths.
  • Branch + commit discipline: Enforces feature-branch work, clean working tree, and conventional-commit subject formats so changes are traceable and ready for PRs.

Quick Start

Run this skill on your feature branch after committing changes so it can verify uv run poe check passes and that no forbidden patterns or prohibited generated-code edits were introduced.

Frequently Asked Questions about quality-gate

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

FAQPage Schema
How do I enforce a zero-tolerance quality gate before creating a pull request?

A zero-tolerance quality gate validates feature branches by running full lint and test suites, scanning diffs for forbidden patterns, and enforcing conventional commits before a PR is created.

What is the best way to prevent skipped tests or type ignore comments in my commits?

Preventing skipped tests and ignore comments requires a pre-done checklist that detects and blocks shortcuts like `# noqa`, `# type: ignore`, or skipped tests, ensuring only clean code is committed.

How do I check branch hygiene and conventional commit formats automatically?

Checking branch hygiene automatically verifies feature-branch usage, working tree cleanliness, and strict conventional-commit subject formats so changes remain traceable and ready for PRs.

Can I run root and MCP server test suites together during pre-PR verification?

Yes, pre-PR verification can execute the complete `uv run poe check` pipeline to run both root and MCP server test suites, ensuring everything passes before proceeding.

Why should my CI checks forbid edits to generated code paths?

CI checks should forbid edits to generated code paths because manual modifications bypass source generation logic, creating inconsistencies that break repository hygiene and safe shipping verification.