mcpField
S
screenshotting-changelog

screenshotting-changelog

github.com/spencerpaulyDevelopment868406 installsUpdated 13w ago
Repository

About screenshotting-changelog

A skill for documenting visual changes in pull requests with before-and-after screenshots, helping reviewers inspect UI updates without running the app.

Key features

  1. 01Capture before-and-after screenshots
  2. 02Create a visual change summary
  3. 03Compare responsive viewport sizes
  4. 04Record themes and interactive states

Use cases

  1. 01Attach screenshots to UI change pull requests
  2. 02Compare mobile, tablet, and desktop layouts
  3. 03Document dark mode or form state changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill screenshotting-changelog

After installing, type/screenshotting-changelogin Claude Code to confirm it loaded.

Details

From the project README

Screenshot Changelog

Use this skill when preparing a pull request that includes visual/UI changes. Capture before and after screenshots to create a visual changelog that reviewers can quickly scan.

Steps

  1. Capture the "before" state — before making changes (or on the base branch), start the dev server and screenshot the affected pages:

    git stash  # or checkout the base branch
    

    Start the dev server, then:

    Tool: browser_navigate
    Arguments: { "url": "http://localhost:3000/affected-page", "take_screenshot_afterwards": true }
    
    Tool: browser_take_screenshot
    Arguments: { "fullPage": true, "filename": "before-homepage.png" }
    

    Repeat for each affected page or component state.

  2. Switch to the feature branch — apply your changes:

    git stash pop  # or checkout the feature branch
    

    Wait for the dev server to hot-reload (or restart it).

  3. Capture the "after" state — screenshot the same pages:

    Tool: browser_take_screenshot
    Arguments: { "fullPage": true, "filename": "after-homepage.png" }
    
  4. Generate the changelog — create a summary describing what changed visually:

    ## Visual Changes
    
    ### Homepage
    **Before:**
    ![before](before-homepage.png)
    
    **After:**
    ![after](after-homepage.png)
    
    Changes: Updated hero section layout, new CTA button color, added testimonials section.
    
  5. Include in the PR description — paste the visual changelog into the PR body so reviewers can see the changes at a glance without running the app locally.

Variations

  • Responsive comparison: use browser_resize to capture screenshots at mobile (375px), tablet (768px), and desktop (1280px) widths.
  • Dark mode comparison: if the app has a dark mode toggle, capture both themes.
  • Interactive states: capture hover states, open modals, filled forms, and error states.

Notes

  • Screenshots are saved to the workspace. You can reference them in markdown or upload them to the PR.
  • For component-level screenshots, navigate to a Storybook URL or a specific component route.
  • This is most valuable for design-heavy PRs — skip it for backend-only changes.

Comments

Markdown supported