skills.rest
joshukraine
joshukraineCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

walkthrough

Generate a browser walkthrough of a PR's user-facing changes.

421|49|Updated Jul 3, 2014
Search Tags:#code review#user experience#PR review#PR testing#browser walkthrough
One-click install
npx skills add https://github.com/joshukraine/dotfiles --skill walkthrough-joshukraine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: walkthrough
Source: https://github.com/joshukraine/dotfiles/tree/main/claude/.claude/skills/walkthrough
Command: npx skills add https://github.com/joshukraine/dotfiles --skill walkthrough-joshukraine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill generates a hands-on browser walkthrough of a PR's user-facing changes, allowing the orchestrator to exercise the feature before the formal code review.

Core Features & Use Cases

  • Generate Walkthrough: Automatically create a step-by-step manual of the PR's user-facing changes.
  • Publish Walkthrough: Optionally publish the final version of the walkthrough to the PR for QA.
  • Use Case: Before merging a PR, the orchestrator can use this Skill to ensure the feature works as expected and identify any UX problems early.

Quick Start

Generate a browser walkthrough for a PR by running: /walkthrough [PR-number-or-branch]

Frequently Asked Questions about walkthrough

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

FAQPage Schema
How do I generate a browser walkthrough for a PR before code review?▼

A PR browser walkthrough maps user-facing changes from a PR diff into a step-by-step manual. It enables orchestrators to exercise features and validate user experience before formal code review.

How can I test user experience changes in a pull request before merging?▼

You test user experience changes by generating a browser walkthrough from the PR diff to map user flows. This lets you exercise features in the browser and identify UX problems early before merging.

Does PR testing require credentials to map user flows for a browser walkthrough?▼

Yes, generating a browser walkthrough requires analyzing the PR diff and mapping user flows and credentials. This ensures the step-by-step manual includes necessary authentication paths for accurate user interface validation.

What is the best way to capture user-facing changes from a PR diff for QA?▼

The best way is to generate a browser walkthrough that analyzes the PR diff and maps user flows. You can optionally publish the resulting step-by-step manual directly to the PR for QA validation.

When should I use a browser walkthrough instead of standard PR review?▼

Use a browser walkthrough when a PR contains user interface changes needing hands-on validation. It complements standard PR review by letting you exercise features and identify UX problems before merging.

Related Skills

Explore More Software Engineering Skills→
koseki2580koseki2580

explain-pr-diff

Build side-by-side HTML walkthroughs from unified diffs explaining PR changes before→after.

Community
Intermediate
abhishekdutta18abhishekdutta18

code-tour

Generate interactive CodeTour .tour files anchored to verified file lines.

Community
Intermediate
patrykk21patrykk21

spec-bugfix-verify

Verify bugfix implementations through automated tests and user confirmation workflows.

Community
Advanced
bdbchbdbch
2

browser-test

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

Community
Intermediate