ck:test

Run automated tests, coverage checks, and build verification for web and Flutter applications.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-test-dthuy62
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:test
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/test
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-test-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of validating software changes by coordinating automated tests, coverage checks, build verification, and quality reporting in one workflow.

Core Features & Use Cases

  • Code Test Execution: Run unit, integration, end-to-end, and regression suites across common stacks, including Flutter, Python, Go, and JavaScript.
  • UI and Visual QA: Verify browser-based user flows, responsive behavior, accessibility, screenshots, and console errors for front-end changes.
  • Coverage and Build Validation: Measure test coverage, confirm production builds, and catch failures early before code is merged or released.
  • Use Case: After a feature or bug fix, use this Skill to check the impacted tests, inspect failures, and produce a concise QA report for the team.

Quick Start

Use ck:test to run the appropriate test workflow for your recent changes and return a structured report with failures, coverage, and build status.

Frequently Asked Questions about ck:test

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

FAQPage Schema
How do I run automated tests and UI QA for Flutter and web applications?

You can validate code changes by running automated unit, integration, and end-to-end tests across common stacks like Flutter, Python, Go, and JavaScript. The workflow measures coverage, verifies production builds, and returns a concise QA report detailing failures and build status.

What is the best way to measure test coverage and catch build failures before merging code?

Measuring test coverage and catching build failures involves running deterministic test suites and build verification checks. This process measures coverage metrics, confirms production builds, and catches failures early before code is merged or released.

Can I perform visual QA and accessibility checks for front-end changes in a single workflow?

Yes, you can perform visual QA and accessibility checks in a single workflow. The process verifies browser-based user flows, responsive behavior, accessibility, screenshots, and console errors to ensure comprehensive front-end UI quality.

Does automated testing work with backend stacks like Python and Go as well as Flutter?

Automated testing works with backend stacks like Python and Go as well as Flutter and JavaScript. The workflow executes unit, integration, and regression suites across these common stacks, requiring deterministic execution to validate software changes accurately.

How do I generate a structured QA report after running regression tests?

To generate a structured QA report after running regression tests, execute the test workflow for your recent changes. The system analyzes failures, measures coverage, verifies builds, and returns a concise report detailing the QA status for your team.