القائمة
Fetch and summarize Diffy diff status, result JSON, changed percentage, per-page and per-breakpoint differences, JUnit output, or recent diff lists. Use when the user asks for diff info, diff results, changed pages, percent changed, report link, or whether a Diffy diff is complete.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Show an existing Diffy project's settings as YAML. Use when the user asks for project details, project settings, project config, "details on project <id>", or to view/get/show/export a project's configuration. Displays the exportable YAML (the dashboard "Export" format), never raw JSON.
Change settings for an existing Diffy project with the diffy CLI. Use when the user asks to update, edit, change, or apply Diffy project settings such as pages, URLs, environments, breakpoints, masks, delays, headers, cookies, login settings, schedules, or multiple project configs.
Compare two environments of a Diffy project server-side with project:compare — Diffy screenshots both environments on its own servers and produces a visual-regression diff, returning a diff ID. Use when the user wants to compare prod vs staging, prod vs a custom/PR/UAT URL, or two arbitrary URLs remotely, without capturing anything locally. This runs on Diffy's servers; to compare a locally running app on THIS machine instead, use the visual-diff skill. If the user is ambiguous about local vs remote, ask.
Create a Diffy visual diff from two existing screenshot set IDs with diff:create. Use when the user asks to compare screenshots, compare two uploaded screenshot sets, create a diff from screenshot IDs, or get a diff ID for before/after screenshots.
Create a Diffy project with the diffy CLI from user-provided project details. Use when the user asks to create a Diffy project, set up a new project in Diffy, or turn a base URL, pages, and breakpoints into a new Diffy project. Requires the user to provide base_url and returns the created project ID.
Trigger Diffy to capture a screenshot set of a project environment on Diffy's own servers (no local browser, no Playwright) with screenshot:create, and return a screenshot ID. Use when the user asks to screenshot production/staging/development or a live custom URL remotely, take Diffy screenshots of an environment, or set a new remote baseline. This runs on Diffy's servers; to capture a locally running app on THIS machine instead, use the upload-screenshot skill. If the user is ambiguous about local vs remote capture, ask.
| name | get-diff-info |
| description | Fetch and summarize Diffy diff status, result JSON, changed percentage, per-page and per-breakpoint differences, JUnit output, or recent diff lists. Use when the user asks for diff info, diff results, changed pages, percent changed, report link, or whether a Diffy diff is complete. |
| allowed-tools | Bash, Read, Write |
Read and summarize Diffy diff information only. Do not create projects, update settings, upload screenshots, or create new diffs in this skill.
diffy from PATH../vendor/bin/diffy exists in the current repo, use that./usr/local/bin may need sudo; Homebrew on Apple Silicon uses
/opt/homebrew/bin):
wget -O /usr/local/bin/diffy https://github.com/diffywebsite/diffy-cli/releases/latest/download/diffy.phar && chmod a+x /usr/local/bin/diffy~/.diffy-cli/diffy-cli.yaml must exist. If it does not, run
diffy auth:login <API_KEY> after the user provides the key (key from https://app.diffy.website/#/keys).Preferred input: DIFF_ID.
If the user gives a project but not a diff ID, list recent diffs:
diffy diff:list <PROJECT_ID> 0
This prints a rendered text table (not JSON) with columns id, changes, state, jobs, estimate, sharedUrl. Read the diff ID from the id column.
Use the latest diff only when the user clearly asked for the latest one. Otherwise ask which DIFF_ID to
inspect.
Status:
diffy diff:get-status <DIFF_ID>
This prints 1 when the diff is complete and nothing (empty output) when it is not — empty output is
not an error, just "not finished yet." For a reliable completion check, read the state field from the
JSON result below.
Top-line changed percentage:
diffy diff:get-changes-percent <DIFF_ID>
Full JSON result:
diffy diff:get-result <DIFF_ID> --format=json
JUnit report, when requested:
diffy diff:get-result <DIFF_ID> --format=junit-xml
Save JSON result to .diffy-skills/diffs/<DIFF_ID>.json before parsing when the user asks for a report or
when the result is large.
Parse these fields from the JSON result:
result: overall percentage of pages changed. 0 means no pages changed.diffSharedUrl: shareable visual report link.name: diff name.state: numeric Diffy state (completed states: 2, 3, 4, 7).diffs: nested map of diffs[url][breakpoint], where each item may contain percentageChanges.Return:
percentageChanges descendingSuggested table columns:
URL | Breakpoint | Changed
/pricing | 375 | 12.4%
/ | 1280 | 1.1%
If there are no non-zero entries, say that no visual changes were reported.
If the diff is not complete, return the current status and tell the user to retry this same skill later. Do not create another diff unless the user explicitly asks for a new comparison.
If you saved the JSON result, it lives under .diffy-skills/; offer to add .diffy-skills/ to the repo's
.gitignore if it is not already ignored.