qa

Run git diff-based QA checks in prescribed order and report failures.

74|14|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/ActiveMemory/ctx --skill qa-activememory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/ActiveMemory/ctx/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/ActiveMemory/ctx --skill qa-activememory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA checks are often skipped or become inconsistent, leading to buggy commits and CI failures. This skill provides a repeatable, guided workflow to validate changes locally before they reach CI.

Core Features & Use Cases

  • Define an ordered QA pipeline (format, vet, lint, test, and optional smoke) to run locally.
  • Reproduce CI failures locally for faster debugging and triage.
  • Use during pre-commit or after code changes to ensure code quality before merging.

Quick Start

Run the QA pipeline locally before committing to catch issues early.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run local QA checks before committing code changes?

Run local QA checks before committing by inspecting changed files with git diff, then executing a prescribed pipeline of format, vet, lint, and test stages. This validates code quality locally and outputs a clear report of any failures to fix before reaching CI.

What is the correct order for running golang format, vet, and lint checks in a pipeline?

The correct order for running golang QA checks is format, vet, lint, test, and an optional smoke stage. Executing these stages in this prescribed sequence ensures consistent validation and reproduces CI issues locally for faster debugging.

Can I reproduce CI test failures locally using a pre-commit QA pipeline?

Yes, you can reproduce CI test failures locally by running the optional smoke stage in the QA pipeline. This executes after format, vet, lint, and test stages to reproduce issues locally, enabling faster triage and a clean commit before pushing changes.

How do I determine which QA checks to run when only specific files have changed?

Determine which QA checks to run by using git diff --name-only to inspect what changed. The pipeline then executes the relevant format, vet, lint, and test stages based on the modified files, outputting a report of any failures and fixes for a clean commit.

Why does my CI pipeline fail when I skip local vet and lint checks?

CI pipelines fail when local vet and lint checks are skipped because inconsistent validation allows buggy commits to reach remote environments. Running a guided QA workflow locally before committing catches these issues early and outputs a clear report of failures and fixes.

What are the limitations of running only format and test stages without vet and lint in golang?

Running only format and test stages without vet and lint in golang limits validation coverage, missing static analysis issues that vet and lint would catch. The prescribed QA pipeline includes all stages to ensure comprehensive code quality checks before a clean commit.