skills.rest
vinhnxv
vinhnxvCOMMUNITY
Explore all skills by this author →
𝕏@vinhnxvGitHub

test-browser

Automate standalone browser E2E testing for changed routes in a PR, branch, or HEAD without spawning an agent team.

6|3|Updated Feb 11, 2026
Search Tags:#automation#testing#e2e#diff#browser#routes
One-click install
npx skills add https://github.com/vinhnxv/rune --skill test-browser-vinhnxv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/vinhnxv/rune/tree/main/plugins/rune/skills/test-browser
Command: npx skills add https://github.com/vinhnxv/rune --skill test-browser-vinhnxv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standalone browser E2E testing for changed routes without spawning an agent team; it provides quick feedback during development by running browser tests inline.

Core Features & Use Cases

  • Maps changed files (PRs, branches, or HEAD) to testable routes and runs browser tests with optional headed mode.
  • Produces per-route results and a concise markdown report, with interactive failure handling and human-gate support when needed.
  • Works in isolation with the ISOLATION CONTRACT, enabling inline execution and easier debugging during development.

Quick Start

Run the /rune:test-browser command to start an inline, headless E2E test loop against your latest changes.

Frequently Asked Questions about test-browser

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

FAQPage Schema
How do I run E2E browser tests for only the changed routes in my current PR?▼

Browser E2E testing for changed routes works by automatically mapping changed files in a PR or branch to testable routes and executing standalone browser tests inline without requiring an agent team.

What is the best way to automate browser tests for changed routes without spawning an agent team?▼

Automating browser tests for changed routes without an agent team is achieved by running an inline, isolation-contract-compliant workflow that discovers affected routes and executes headless or headed browser tests directly.

Does this browser testing workflow support headed mode for debugging E2E test failures?▼

Headed mode is supported for browser E2E testing, allowing interactive failure handling and easier debugging during development by providing a human gate for resolving issues within the inline test loop.

How do E2E browser tests map changed files to testable routes in a branch?▼

Changed files in a branch or HEAD are mapped to testable routes through enforced scope resolution and route discovery, ensuring browser E2E tests target only the affected application paths and produce per-route results.

Can I get a markdown report of per-route E2E browser test results for my latest changes?▼

A concise markdown report is generated alongside per-route results after running browser E2E tests, summarizing the testing outcomes for your latest changes and providing quick feedback during development.

Are there limitations to running standalone browser E2E tests inline during development?▼

Standalone browser E2E tests run inline using an isolation contract to avoid spawning agent teams, meaning complex multi-agent orchestration scenarios fall outside the intended scope of this quick feedback workflow.

Related Skills

Explore More Software Engineering Skills→
jpoleyjpoley
50

security-reporter

Consolidates vulnerability findings into audit reports with risk assessment and compliance mapping.

Community
Advanced
uesleinaschuesleinasch

unac-fix-blockers

Orchestrate fixes for blocking issues from code review reports.

Community
Advanced
betaTridentbetaTrident

browser-qa

Automate visual regression testing and UI interaction verification for web applications.

Community
Advanced
fgarofalo56fgarofalo56
6

testing

Run unit, integration, and E2E tests with pytest, Jest, Cypress, and Playwright.

Community
Advanced