e2e-help

Discover E2E pipeline commands and file documentation feedback as GitHub issues.

3|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/iamcxa/kc-claude-plugins --skill e2e-help
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-help
Source: https://github.com/iamcxa/kc-claude-plugins/tree/main/e2e-pipeline/skills/e2e-help
Command: npx skills add https://github.com/iamcxa/kc-claude-plugins --skill e2e-help

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users discover, understand, and navigate the E2E pipeline command surface and report documentation gaps so teams can find commands, read authoritative topics, and file actionable feedback without leaving the testing workflow.

Core Features & Use Cases

  • Live command discovery: Reads SKILL.md frontmatter across skills/* to extract command names and short descriptions for an always-up-to-date reference.
  • Topic mapping & deep dives: Scans docs/*.md, resolves keyword aliases, and presents topic summaries or full doc excerpts for targeted help.
  • Feedback collection & triage: Classifies feedback as doc-gap, feature-request, or bug, drafts a proposed GitHub issue, attempts to create it via gh, and falls back to local logging if gh is unavailable.
  • Use case: Onboarded QA or developer needs a quick command reference, deeper documentation on a topic, or an easy way to report missing or unclear docs.

Quick Start

Use /e2e-help to list available commands, view a topic deep dive by name, or submit feedback with /e2e-help --feedback "describe the gap".

Frequently Asked Questions about e2e-help

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

FAQPage Schema
How do I discover available E2E pipeline commands for testing workflows?

You can discover E2E pipeline commands by reading the SKILL.md frontmatter across skills directories to extract command names and short descriptions for an always-up-to-date reference. This ensures you get live command discovery without manually checking individual files.

What is the best way to report documentation gaps or missing E2E testing topics?

The best way to report documentation gaps is to classify feedback as doc-gap, feature-request, or bug, draft a proposed GitHub issue, and attempt to create it via gh. If gh is unavailable, it falls back to local logging to preserve your feedback.

How do I find deep dive documentation for specific E2E testing topics?

To find deep dive documentation, scan docs markdown files, resolve keyword aliases, and present either topic summaries or full doc excerpts. This mapping provides targeted help by surfacing authoritative topics directly during your testing workflow.

Does the E2E help feedback system require the GitHub CLI to file issues?

No, the E2E help feedback system does not require the GitHub CLI because it falls back to local logging if gh is unavailable. It attempts to create the issue via gh first, but ensures your feedback is still recorded locally if the tool is missing.

Why should QA teams use an interactive command reference during E2E testing?

QA teams should use an interactive command reference because it reads frontmatter across skills to provide an always-up-to-date list of command names and descriptions. This allows onboarding users to quickly find commands without leaving the testing workflow.