skills.rest
DotanVG
DotanVGCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

golden-path

Automate the manual browser QA smoke test for Orbital Breach gameplay changes.

2|Updated Apr 7, 2026
Search Tags:#qa#regression#gameplay#smoke-test#manual-testing#orbital-breach
One-click install
npx skills add https://github.com/DotanVG/Orbital-Breach --skill golden-path-dotanvg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: golden-path
Source: https://github.com/DotanVG/Orbital-Breach/tree/main/.claude/skills/golden-path
Command: npx skills add https://github.com/DotanVG/Orbital-Breach --skill golden-path-dotanvg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Walkthrough the Orbital Breach manual browser QA smoke test to ensure changes to gameplay and UI are verified consistently and quickly.

Core Features & Use Cases

  • Manual QA checklist for core gameplay flows including movement, shooting, grabbing, launching, and breach win validation.
  • Regression verification to confirm that fixes or changes do not reintroduce known issues.
  • Documentation trail to capture verification outcomes and discrepancies for future audits.

Quick Start

Follow the manual browser QA checklist to validate all core gameplay changes in the dev environment.

Frequently Asked Questions about golden-path

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

FAQPage Schema
How do I run a manual smoke test for gameplay changes in Orbital Breach?▼

Orbital Breach manual QA smoke testing verifies that code changes touching gameplay, controls, camera, breach logic, or UI do not introduce regressions. It provides a checklist to validate core flows like movement, shooting, and breach win conditions.

What gameplay flows should I verify during an Orbital Breach smoke test?▼

As part of manual browser QA, the smoke test verifies core gameplay flows including movement, shooting, grabbing, launching, and breach win validation. It documents discrepancies and validation outcomes for future audits.

How do I document regression testing outcomes for browser gameplay fixes?▼

The Orbital Breach smoke test provides a documentation trail to capture verification outcomes and discrepancies for future audits. It confirms that fixes or changes do not reintroduce known issues during manual browser QA.

When should I run a manual smoke test for my game's UI and camera changes?▼

You should apply the Orbital Breach smoke test during code changes that touch gameplay, controls, camera, breach logic, or UI. This ensures correctness and verifies that changes do not reintroduce known issues.

Can I use this QA checklist to verify breach logic and controls in a dev environment?▼

Yes, the Orbital Breach manual smoke test is applied in the dev environment to verify changes to controls and breach logic. It automates the manual browser QA checklist to ensure correctness and traceability of fixes.

Related Skills

Explore More Software Engineering Skills→
DotanVGDotanVG
2

arena-debug

Reproduce and diagnose zero-G gameplay bugs in Orbital Breach.

Community
Intermediate
FlintmereFlintmere

fix-bug

Reproduce reported defects in Flintmere's codebase and validate fixes with regression tests.

Official
Advanced
manastalukdarmanastalukdar
1

pipeline-monitor

Analyze CI/CD pipeline build success rates, flaky tests, and duration trends.

Community
Advanced
bdbchbdbch
2

browser-test

Execute manual browser tests in Chrome with navigation, form interactions, and state verification.

Community
Intermediate