본문으로 건너뛰기
cccskills
무료GitHub에 공개

before-and-after

Capture two web pages or image files for a visual comparison. Choose a page element with a CSS selector, set a mobile, tablet, or custom viewport, and create a Markdown comparison for PRs when needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Captures before/after screenshots of web pages or elements for visual comparison. Use when user says "take before and after", "screenshot comparison", "visual diff", "PR screenshots", "compare old and new", or needs to document UI changes. Accepts two URLs (file://, http://, https://) or two image paths.

michaelshimeles/rstack스타 1,392(GitHub 1,392 + cccskills 0)
연동 도구GitHubVercel

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Compare UI before and after a change
  • Capture a specific page element
  • Prepare screenshot evidence for a PR
  • Compare mobile or tablet layouts

포함된 파일(5)

  • SKILL.md4.4 KB
  • LICENSE1.2 KB
  • scripts/adapters/0x0st.sh728 B
  • scripts/adapters/blob.sh1.3 KB
  • scripts/upload-and-copy.sh3.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Before-After Screenshot Skill

Package: @vercel/before-and-after Never use before-and-after (wrong package).

Agent Behavior Rules

DO NOT:

  • Switch branches or stash another task's changes. Use an isolated worktree for any baseline server already authorized by the task.
  • Use --full unless user explicitly asks for full page / full scroll capture

DO:

  • Use --markdown when user wants PR integration or markdown output
  • Use --mobile / --tablet if user mentions phone, mobile, tablet, responsive, etc.
  • Reuse before captures, baseline URLs, and revision information already established in the task. Confirm that they show the relevant behavior and match the after capture's viewport and starting state.
  • Treat the current state as after only when the task context establishes it. If the before state remains ambiguous after checking available context, ask for the missing baseline. Do not ask again for a URL when a valid image pair or earlier baseline is already available.

Capture and delivery

  1. Use an installed before-and-after CLI or npx @vercel/before-and-after.
  2. For remote URLs, check access when needed. A 401/403 indicates protection. Existing image pairs do not require a URL or deployment access check.
  3. Capture missing images with before-and-after "<before-url>" "<after-url>".
  4. When the task calls for uploaded evidence or PR markdown, run before-and-after before.png after.png --markdown once. For local capture requests, deliver the files without uploading them.
  5. Append the markdown to the PR when PR integration is part of the task.

Resolve bundled script paths relative to this skill's directory, not the project working directory. Reuse earlier evidence instead of recapturing it.

Quick Reference

# Basic usage
before-and-after <before-url> <after-url>

# With selector
before-and-after url1 url2 ".hero-section"

# Different selectors for each
before-and-after url1 url2 ".old-card" ".new-card"

# Viewports
before-and-after url1 url2 --mobile    # 375x812
before-and-after url1 url2 --tablet    # 768x1024
before-and-after url1 url2 --full      # full scroll

# From existing images
before-and-after before.png after.png --markdown

# Via npx (use full package name!)
npx @vercel/before-and-after url1 url2
FlagDescription
-m, --mobileMobile viewport (375x812)
-t, --tabletTablet viewport (768x1024)
--size <WxH>Custom viewport
-f, --fullFull scrollable page
-s, --selectorCSS selector to capture
-o, --outputOutput directory (default: ~/Downloads)
--markdownUpload images & output markdown table
--upload-url <url>Custom upload endpoint (default: 0x0.st)

Image Upload

# Default (0x0.st - no signup needed)
./scripts/upload-and-copy.sh before.png after.png --markdown

Vercel Deployment Protection

If .vercel.app URL returns 401/403:

  1. Check Vercel CLI: which vercel && vercel whoami
  2. If available: vercel inspect <url> to get bypass token
  3. If not: Tell user to provide bypass token, take manual screenshots, or disable protection

PR Integration

# Check for gh CLI
which gh

# Get current PR
gh pr view --json number,body

# Write the existing body plus the comparison to a temporary file, then:
gh pr edit <number> --body-file /path/to/pr-body.md

If no gh CLI: output markdown and tell user to paste manually.

Error Reference

ErrorFix
command not foundnpm install -g @vercel/before-and-after
could not determine executableUse npx @vercel/before-and-after (full name)
401/403 on .vercel.appSee Vercel protection section
Element not foundVerify selector exists on page

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use this guide to decide when repeated operational code should become a shared service, while keeping product rules in the workflow actions that own them. It provides practical design principles and a gradual migration checklist to preserve existing boundaries and behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Deciding whether duplicated workflow code should be extracted
  • Separating business rules from reusable operations
  • Planning a gradual refactor across multiple callers
michaelshimeles/rstack1.4천2026년 10월 26일 업데이트

Verify changed behavior with evidence suited to the task: a live screen recording for interactive UI flows, scripted captures for headless checks, or measured outputs for non-UI changes. Create a results report and send the evidence to the requested destination when authorized.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Capturing a live recording of a UI test
  • Checking a UI flow in a headless environment
  • Comparing measured API or performance results
michaelshimeles/rstack1.4천2026년 10월 26일 업데이트

greploop

무료

Review Greptile feedback on a pull request, merge request, or shelved changelist, then make scoped fixes and request fresh reviews within a set cycle limit. Track actionable findings and report the current score, checks, and any work left unresolved.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Working through Greptile feedback on a pull request
  • Fixing actionable review findings on a merge request
  • Reviewing a Perforce changelist with Greptile
michaelshimeles/rstack1.4천2026년 10월 26일 업데이트

Run the existing `greploop` workflow with the `@greptile-apps` trigger when the usual trigger cannot handle a large pull request. This entrypoint depends on the separate `greploop` skill and adds no workflow of its own.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Run greploop on a large PR
  • Use the Greptile Apps trigger
  • Continue an existing greploop review
michaelshimeles/rstack1.4천2026년 10월 26일 업데이트

Prepare an isolated Git worktree and branch for each feature, fix, or documentation task. Check for an existing assignment and overlapping pull requests first, so edits stay scoped to the right work and do not build on another task’s changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Starting a feature in its own worktree
  • Fixing a bug without editing the shared checkout
  • Checking for overlapping pull request changes
michaelshimeles/rstack1.4천2026년 10월 26일 업데이트

unslop

무료

Edit text for people to remove common AI writing patterns while keeping its meaning and intended tone. The skill checks for vague claims, formulaic phrasing, filler, and stiff language, then revises the text with more specific wording and varied rhythm.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Polish a commit message before committing
  • Make a PR title and body sound natural
  • Revise docs or code comments for human readers
michaelshimeles/rstack1.4천2026년 10월 26일 업데이트

michaelshimeles의 스킬 모두 보기

이 스킬의 문제 신고