Skip to content
cccskills
FreePublished on GitHub

e2e-artifact-handling

E2E artifact handling routing. Use when traces, videos, screenshots, reports, or failure bundles need controlled repository-local placement; do not use for simple unit tests or production-mutating E2E flows.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

E2E Artifact Handling

Use this skill to define one bounded E2E evidence-collection/packaging need. ROSE may assign it to one fresh e2e-artifact-runner context after the delegation gate; this skill does not dispatch or invoke another process skill.

Trigger

  • E2E command needs trace/video/screenshot/report/failure-bundle evidence.
  • A failing browser flow needs artifacts for ROSE review.
  • User asks to preserve test artifacts from an E2E run.

Required Safety Gate

  • Use localhost, fixtures, or explicitly approved non-production/read-only targets.
  • Require repository-local artifact placement before writing user-visible screenshots, traces, videos, reports, or bundles.
  • Do not create new tests/e2e/, report, trace, screenshot, or golden directories without placement approval.
  • Redact or avoid artifacts containing secrets, cookies, tokens, credentials, or private user data.

Near Misses

  • Browser QA without durable artifacts, test design/unit/integration verification, or coverage review are different primary intents; return the exact mismatch to ROSE.

Required Routing

  • Canonical owner: ROSE/aili-delivery-flow; direct artifact handling is preferred when no specialist context is needed.
  • Optional agent: one fresh, terminal e2e-artifact-runner assignment after a new benefit decision; no resume, automatic retry, or final-verdict ownership.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review a single academic paper, preprint, DOI, arXiv link, or user-provided PDF/text with source-grounded critique. Use for paper summaries, methodology review, novelty checks, reproducibility concerns, or "review this paper" requests; do not use for multi-paper surveys, systematic literature reviews, citation management, or implementation from a paper.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

AI regression scouting routing. Use when agents, prompts, skills, model/tool routing, harness fixtures, or generated-output expectations change and need regression scenarios; do not use for ordinary product-code regressions.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Run the AILI delivery lifecycle from natural-language IDEATE, DEFINE, BUILD, and SHIP intent or the equivalent slash shortcuts; use for idea shaping, spec/test definition, bounded BUILD package queues, review-repair closeout, or adapter routing without exposing internal stage commands.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Android native Kotlin/Compose app development, Material 3 UI, accessibility, and Gradle builds.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Route an explicitly requested independent/delegated browser QA assignment or durable E2E evidence need; do not trigger for direct Playwright/DOM/console/network inspection, ordinary UI implementation, backend-only work, or production-mutating flows.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

See all skills by Rosetears520

Report a problem with this skill