e2e-skill-ops

Diagnose e2e skill failures and maintain cross-skill consistency.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates ambiguity and manual guesswork when end-to-end test skills fail or drift by enforcing known-issue lookup, cross-skill impact scanning, verified fixes, and persistent knowledge capture so teams can reliably repair and evolve e2e pipelines.

Core Features & Use Cases

  • Systematic Diagnosis: Guided debug flows that search prior findings, classify symptoms (mapping, flow, skill, environment), and capture evidence for reproducible fixes.
  • Cross-Skill Impact Scanning: Mandatory impact matrix that enumerates related skills, agents, and references to prevent silent regressions when changing any e2e skill.
  • Verified Fixes & Knowledge Capture: Re-run failing steps for verification, append findings to skill-quality-findings.md and shared learned-patterns, and require human approval before altering shared plugin files.
  • Use Cases: Debugging intermittent test failures, syncing changes after editing skill instructions, adding new e2e capabilities, and running post-suite gap analyses.

Quick Start

Invoke the skill by describing the failure or running /e2e-skill-ops --debug, --maintain, --add-feature, or --evaluate to perform the chosen operation.

Frequently Asked Questions about e2e-skill-ops

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

FAQPage Schema
How do I debug end-to-end test failures systematically without manual guesswork?

To debug end-to-end test failures systematically, use guided debug flows that search prior findings, classify symptoms into mapping or environment issues, and capture evidence for reproducible fixes.

What is cross-skill impact scanning and when do I need it for e2e pipeline maintenance?

Cross-skill impact scanning is an impact matrix that enumerates related skills, agents, and references to prevent silent regressions. You need it when changing any e2e skill to maintain consistency.

How do I add new e2e capabilities while preventing regressions in existing pipeline skills?

To add new e2e capabilities safely, perform an impact-matrix scan to enumerate affected skills, re-run failing steps for verification, and require human approval before altering shared plugin files.

Does this e2e skill ops workflow require human approval before modifying shared plugin files?

Yes, the e2e skill ops workflow enforces human approval before changing shared plugin files, ensuring verified fixes and preventing unauthorized modifications to shared learned-patterns.

Why do my intermittent e2e test failures keep recurring across different pipeline runs?

Intermittent e2e test failures recur when prior findings are not consulted and fixes are not verified. Appending findings to skill-quality-findings.md and re-running failing steps captures knowledge to prevent recurrence.

What's the best way to run a post-suite gap analysis for e2e test skills?

The best way to run a post-suite gap analysis is to invoke the evaluate operation, which performs impact-matrix scans, verifies failing steps, and appends findings to skill-quality-findings.md.