quality-gate

Run quality checks on changed Go packages and report structured verdicts.

5|5|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/erraggy/oastools --skill quality-gate-erraggy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/erraggy/oastools/tree/main/.claude/skills/quality-gate
Command: npx skills add https://github.com/erraggy/oastools --skill quality-gate-erraggy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run the complete quality validation pipeline (make check and gopls diagnostics) and report structured pass/fail results for changed Go packages, reducing manual QA overhead.

Core Features & Use Cases

  • Identify scope of changed Go packages by inspecting git changes
  • Run make check to validate formatting, tidy, lint, and tests
  • Run gopls diagnostics on changed files and categorize results
  • Produce a concise verdict and actionable follow-ups

Quick Start

Run the quality gate on all changed Go packages to validate and report results.

Frequently Asked Questions about quality-gate

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

FAQPage Schema
How do I automate quality validation for changed Go packages?▼

To automate quality validation for changed Go packages, you can run a quality gate that inspects git changes, executes make check, and runs gopls diagnostics to report structured pass/fail results.

What does the make check command validate in a Go project?▼

The make check command validates Go project formatting, dependency tidy state, linting rules, and test execution to ensure code quality standards are met before integration.

Can I run gopls diagnostics on specific changed files instead of the whole repository?▼

Yes, you can run gopls diagnostics on targeted groups of changed files. The quality gate identifies changed packages by inspecting git changes and applies diagnostics selectively to those boundaries.

How do I get structured pass or fail results for Go code quality checks?▼

You can get structured pass or fail results by running a quality gate that outputs a concise verdict alongside per-file findings, categorizing gopls diagnostics and make check results for actionable follow-ups.

Does this quality gate require any external dependencies to run?▼

No, this quality gate does not require external dependencies. It operates by leveraging your existing Go environment, utilizing make check and gopls directly to evaluate changed packages.

Why should I use an automated quality gate instead of running checks manually?▼

Using an automated quality gate reduces manual QA overhead by identifying the exact scope of changed Go packages, determining module boundaries, and producing structured per-file findings automatically.