ck:test

Run comprehensive test suites and generate structured markdown QA reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-test-nam3886
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:test
Source: https://github.com/nam3886/golang-echo-boilerplate/tree/main/.claude/skills/test
Command: npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-test-nam3886

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Projects lack a consistent, repeatable way to execute unit, integration, end-to-end, and UI tests while producing actionable coverage metrics and QA summaries; this skill centralizes test execution, coverage analysis, visual checks, and structured reporting so teams can validate changes and catch regressions before release.

Core Features & Use Cases

  • Unified Test Execution: Orchestrates unit, integration, and e2e test runs across languages and runners with clear pass/fail outcomes.
  • Coverage & Build Verification: Generates coverage metrics, enforces thresholds, and validates builds to prevent regressions.
  • UI & Visual Testing: Drives browser automation for screenshots, responsive checks, and accessibility audits via ck:chrome-devtools.
  • Use Case: After a feature branch is pushed, run a full test suite, collect coverage reports, run UI visual checks on critical flows, and produce a concise QA report with failing test details and remediation notes.

Quick Start

Run a full suite of unit, integration, and e2e tests, generate coverage metrics, and produce a QA markdown report with failing test details and screenshots.

Frequently Asked Questions about ck:test

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

FAQPage Schema
How do I run end-to-end and unit tests with coverage analysis and generate a QA report?

To run end-to-end and unit tests with coverage analysis, this skill orchestrates test suites across runners, collects coverage metrics, and outputs a markdown QA report with pass/fail outcomes and remediation notes.

What is UI visual regression testing and how does it work with browser automation?

UI visual regression testing captures screenshots during browser automation to detect visual changes. This skill drives browser automation via ck:chrome-devtools to perform responsive checks and accessibility audits on critical flows.

Does this test execution and QA reporting tool support Go and common test runners?

Yes, this test execution and QA reporting tool integrates with Go and common test runners, orchestrating unit, integration, and e2e test runs while validating builds to prevent regressions.

Can I enforce coverage thresholds and validate builds to prevent regressions?

Yes, you can enforce coverage thresholds and validate builds to prevent regressions. The skill generates coverage metrics and validates builds during the test suite execution phase.

What's the best way to automate test execution and generate a markdown QA report after a feature branch push?

The best way to automate test execution after a feature branch push is using this skill to run full test suites, collect coverage metrics, execute UI visual checks, and produce a concise markdown QA report with failing test details.

Why do I need a centralized test runner for unit, integration, and e2e testing?

You need a centralized test runner because projects lack a consistent, repeatable way to execute tests while producing actionable coverage metrics. This approach centralizes execution, visual checks, and structured reporting to catch regressions before release.