journey

Extract steps from GitHub or GitLab issues and run Playwright tests.

1|Updated Mar 3, 2026

Search Tags:#github #issue tracking #playwright #end-to-end testing #gitlab

One-click install

npx skills add https://github.com/RebelliousSmile/my-claude-marketplace --skill journey-rebellioussmile

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: journey
Source: https://github.com/RebelliousSmile/my-claude-marketplace/tree/main/plugins/overcode/skills/journey
Command: npx skills add https://github.com/RebelliousSmile/my-claude-marketplace --skill journey-rebellioussmile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, gitlab, playwright, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the execution of user journeys from GitHub or GitLab issues, logging results to a structured report and posting a summary to the issue.

Core Features & Use Cases

End-to-End Testing: Validates feature functionality against issues using Playwright.
Automated Reporting: Generates and logs test results step-by-step.
Issue Update: Posts summary and conclusion directly to the issue for review.
Use Case: Ideal for validating features through user journeys linked to specific issues in GitHub or GitLab.

Quick Start

Run the journey for issue #123.

Frequently Asked Questions about journey

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

FAQPage Schema

How do I automate end-to-end testing for GitHub or GitLab issues?▼

To automate end-to-end testing for GitHub or GitLab issues, this Skill extracts steps from issue descriptions, generates Playwright test scripts, executes them, and logs structured results to a report.

Can I validate user journeys linked to specific GitLab issues automatically?▼

Yes, you can validate user journeys linked to specific GitLab issues automatically. The Skill executes the journeys with Playwright and posts a summary and conclusion directly back to the issue for review.

Do I need GitHub or GitLab API access to run Playwright end-to-end tests from issues?▼

Yes, you need GitHub or GitLab API access to run these Playwright end-to-end tests. API access is required to extract issue descriptions and post the automated test summary back to the issue.

How does automated issue testing handle test results and reporting?▼

Automated issue testing handles reporting by logging test results step-by-step into a structured report. It generates this report after executing the extracted user journeys with Playwright.

What's the best way to validate feature functionality against GitHub issues?▼

The best way to validate feature functionality against GitHub issues is to run automated user journeys with Playwright. This approach tests the features directly and posts a conclusion summary to the issue.