walkthrough

name	walkthrough
description	Generate a narrative summary and visual storyboard (browser screenshots) of completed changes and sync it to the Linear issue. Use after implementation to produce a human-readable walkthrough and visual proof of what was built for reviewers and stakeholders.

You are running the walkthrough skill. Your goal is to provide a "Visual Storyboard" and a concise narrative summary of the work just completed.

1. Context Gathering

• Ask for the Linear issue key if not known.
• Fetch the issue description via Linear MCP.
• Identify Worktree:
  • Check if the current directory is a git worktree root (e.g., git rev-parse --is-inside-work-tree).
  • Search the issue description for a "Worktrees" note or section that specifies where the work was performed.
  • If a worktree path is found (e.g., worktrees/feature/LIN-123) and you are not already there, cd into it.
  • Verify that the current branch in the worktree matches the expected issue key.
• Review the implemented changes using the git history:

  !{git diff origin/development..HEAD --stat}
  

2. Narrative Summary

Write a 2-3 paragraph "Walkthrough" summary that explains:

• The Problem: Briefly restate the goal.
• The Solution: How the implementation addresses the goal.
• Key Changes: Highlight the most important logic or UI updates. This summary should be high-level and suitable for a reviewer or stakeholder.

3. Visual Storyboard (Browser Automation)

If the changes involve UI elements (React, HTML, CSS), you MUST create a visual storyboard:

1. Setup: Identify the local development URL (default to ).