skills.rest
notque
notqueCOMMUNITY
Explore all skills by this author →
GitHub

go-pr-quality-gate

Run Go PR quality checks via the repository's Makefile check target.

415|44|Updated Mar 18, 2026
Search Tags:#go#quality#pr#lint#gate#ci#tests
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill go-pr-quality-gate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: go-pr-quality-gate
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/go-pr-quality-gate
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill go-pr-quality-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Go projects often ship PRs without a consistent quality gate, which leads to undetected linting, build, and test issues not surfaced before merging. This Skill provides a deterministic quality gate by running make check and structuring the results into actionable feedback for PR reviews.

Core Features & Use Cases

  • Deterministic execution: always rely on make check as the single source of truth.
  • Structured feedback: categorize linting, tests, and build errors with clear, actionable fixes.
  • Coverage extraction: parse and report test coverage from check output.
  • Prerequisite validation: verify go.mod and Makefile exist before executing checks.
  • Report formats: output JSON or human-readable text for automation and reviews.

Quick Start

Run the Go PR quality gate against a Go repository by invoking the repository's Makefile check target.

Frequently Asked Questions about go-pr-quality-gate

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

FAQPage Schema
How do I run deterministic Go PR quality checks?▼

Deterministic Go PR quality checks run by executing the repository's Makefile check target, enforcing a single source of truth for linting, tests, and build validation during PR review.

What is the best way to structure Go linting and test feedback for pull requests?▼

Structuring Go PR feedback involves categorizing linting, tests, and build errors from the check output into actionable fixes, reporting exact exit codes, and extracting coverage data.

Do I need a Makefile to automate Go CI tests and coverage extraction?▼

Yes, you need a Makefile with a check target and a go.mod file. The quality gate prerequisite validation checks for these files before executing any Go tests or extracting coverage.

Can I output Go test coverage and linting results as JSON?▼

Yes, you can output Go test coverage and linting results as JSON or human-readable text, enabling both automated CI pipelines and direct human review of the structured feedback.

Why does my Go PR quality gate fail to suggest targeted fixes for lint errors?▼

Targeted fix suggestions rely on parsing standard linting outputs and the repository's references data; if the Makefile check target does not generate standard lint output, suggestions cannot be generated.

Related Skills

Explore More Software Engineering Skills→
0xharryriddle0xharryriddle
3

git-run-checks

Auto-detect repository toolchains and run lint, typecheck, test, and build checks.

Community
Advanced
codejunkie99codejunkie99
101

gf-lint

Lint SystemVerilog code with Verilator and produce categorized warnings and errors.

Community
Intermediate
ManfronEnricoManfronEnrico

workspace-enforce

Block merges when high-severity workspace violations lack waivers.

Community
Advanced
maksimzayatsmaksimzayats
200

specx-project-tooling

Generate pyproject.toml and Makefile with Ruff, mypy, and pytest for Specx services.

Community
Intermediate