Cursor Skill

screenshotting-changelog

Generate a visual changelog or PR description by taking before/after screenshots of UI changes using Cursor's built-in browser. Use when preparing a PR with visual changes.

LLM Mart · 0 points · 23 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download spencerpauly-awesome-cursor-skills-resources_screenshotting-changelog-99cd265.zip · 1 KB
Part of spencerpauly/awesome-cursor-skills — 65 skills

Install

skills CLI npx skills add https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/screenshotting-changelog
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install spencerpauly-awesome-cursor-skills@llmmart
Git git clone https://github.com/spencerpauly/awesome-cursor-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole spencerpauly/awesome-cursor-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.
Files (awesome-cursor-skills)
  • SKILL.md 2.4 KB
    ---
    name: screenshotting-changelog
    description: Generate a visual changelog or PR description by taking before/after screenshots of UI changes using Cursor's built-in browser. Use when preparing a PR with visual changes.
    ---
    
    # 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:
    
       ```bash
       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:
    
       ```bash
       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:
    
       ```markdown
       ## 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 (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related