skills.rest
HuXiangyu123
HuXiangyu123COMMUNITY
Explore all skills by this author →
GitHub

cli-e2e-testcase-writer

Generate deterministic Go CLI E2E test workflows and coverage.md per domain.

3|1|Updated Apr 23, 2026
Search Tags:#automation#testing#e2e#cli#go#coverage#workflows
One-click install
npx skills add https://github.com/HuXiangyu123/CUA-Lark-Agent --skill cli-e2e-testcase-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-e2e-testcase-writer
Source: https://github.com/HuXiangyu123/CUA-Lark-Agent/tree/main/lark-cli/tests/cli_e2e/cli-e2e-testcase-writer
Command: npx skills add https://github.com/HuXiangyu123/CUA-Lark-Agent --skill cli-e2e-testcase-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Go CLI End-to-End test writer provides a standardized, repeatable way to generate domain-specific E2E test workflows and coverage artifacts for lark-cli, reducing manual setup and ensuring consistency across domains.

Core Features & Use Cases

  • Generate domain-scoped workflow testcases under tests/cli_e2e/{domain}/
  • Create or update coverage.md for the chosen domain
  • Reuse shared E2E support code and reference domain patterns to accelerate testing
  • Treat tests/cli_e2e/demo/ as reference only

Quick Start

Run the cli-e2e-testcase-writer on a domain to generate workflow testcases and coverage.

Frequently Asked Questions about cli-e2e-testcase-writer

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

FAQPage Schema
How do I generate Go CLI E2E tests for a specific domain?▼

The tool generates deterministic Go CLI E2E test workflows for a single domain by placing testcases under tests/cli_e2e/{domain}/. It enforces domain scoping and produces a coverage.md file while reusing shared E2E support code.

What is the best way to track E2E test coverage for Go CLI workflows?▼

Tracking E2E test coverage for Go CLI workflows involves generating a domain coverage.md artifact alongside your testcases. This approach provides structured coverage tracking for each specific domain within the tests/cli_e2e directory.

Can I reuse shared E2E support code across different domain tests?▼

Yes, you can reuse shared E2E support code across different domain tests. The generator reuses existing E2E support code located under tests/cli_e2e to accelerate testing and ensure consistency across domains.

Does the Go CLI E2E test generator support required binaries?▼

Yes, the Go CLI E2E test generator supports required binaries through metadata.requires. This ensures any necessary binaries are defined and available for the domain-specific workflow testcases.

When should I not use automated Go CLI E2E test generation?▼

You should not use automated Go CLI E2E test generation when creating cross-domain test workflows, as this generator strictly enforces single-domain scoping. It is designed for per-domain runs rather than global test suite creation.

Related Skills

Explore More Software Engineering Skills→
filimorniga-uxfilimorniga-ux

qa-testing-enforcer

Enforce Vitest and Playwright test coverage for new or modified code artifacts.

Community
Advanced
MolcajeteAIMolcajeteAI
2

coverage-analysis

Execute Go tests with coverage flags and generate detailed coverage reports.

Official
Basic
openkaidenopenkaiden
10

testing-commands

Test Go/Cobra CLI commands with unit and end-to-end tests.

Official
Advanced
eykdeykd

quality-review

Review GitHub pull requests for correctness, style, test coverage, and standards.

Community
Advanced