diff

Diffs live page accessibility violations against a git baseline and reports new, fixed, and pre-existing issues.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Debindenny/travelplanner-community- --skill diff-debindenny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diff
Source: https://github.com/Debindenny/travelplanner-community-/tree/main/travel-planner/claude-marketplace/plugins/accesslint/skills/diff
Command: npx skills add https://github.com/Debindenny/travelplanner-community- --skill diff-debindenny

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @accesslint/cli, @accesslint/chrome.

What problem does it solve? When you change code, you need to know whether your changes introduced new accessibility violations or fixed old ones, without wading through a full audit report. This Skill compares a live page's accessibility violations against a baseline (uncommitted changes via git stash, or another branch) and reports only what changed. ## Core Features & Use Cases - Stash-based diffing: Stashes uncommitted changes to capture a baseline scan, restores your working tree, then reports new, fixed, and pre-existing violations. - Branch diffing: Checks out a target branch (defaulting to the repo's default branch) to capture the baseline, with --wait-for support to gate audits on rebuilds. - Actionable reporting: Each new violation includes the selector, source location when available, evidence, and a mechanical fix or a NEEDS HUMAN flag. - Use Case: Before committing a UI change, run the diff to confirm your new component did not introduce color-contrast or missing-alt violations compared to main. ## Quick Start Ask the AI to diff the accessibility violations of your local page against the main branch, for example: "Run an accessibility diff of http://localhost:3000 against main and show only new violations."

Frequently Asked Questions about diff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my code changes introduced new accessibility violations?▼

Run the diff skill with no arguments to compare your uncommitted changes against a stashed baseline. It scans the page twice and reports only new violations, fixed violations, and the count of pre-existing ones.

How to diff accessibility issues between two git branches?▼

Pass --branch with a branch name, or omit the value to use the repository's default branch. The skill checks out that branch to capture a baseline scan, restores your working tree, then scans the current state and reports the delta.

Why does the accessibility diff show a stale or identical baseline?▼

In stash mode, hot module replacement may not have finished before the second scan; the built-in sleep covers most cases. In branch mode, add --wait-for with a CSS selector to gate the audit until the rebuild completes.

Does the accessibility diff modify my working tree?▼

It temporarily stashes uncommitted changes or checks out another branch to capture the baseline, then restores everything with git stash pop or git checkout. Your working tree is fully restored after the run.

When should I use a full accessibility scan instead of a diff?▼

Use a full scan when you need a complete audit with no baseline comparison, or when heavy DOM changes between runs cause selector drift that makes the diff unreliable. The diff only reports what changed.