home / Design / Accesslint Diff Skill by @sickn33

Accesslint Diff Skill by @sickn33

FREE

github stars★ 48,690updatedOct 2026repo@sickn33

activity (commits, last 6 months)

6mo ago0

this month1

$git clone https://github.com/sickn33/agentic-awesome-skills

The skill is the skills/accesslint-diff folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.

about Accesslint Diff Skill by @sickn33

Diff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based).

our take

Compares a live page's accessibility violations against a baseline, by default using uncommitted changes, or a branch if you pass one. It reports only new violations, which keeps the output focused on regressions.

when to use it

You want to catch accessibility regressions in a change
You review a branch for new violations only
You need a check that fits a pull request routine

before you install

Relies on stashing and isolated snapshots, so read its gotchas section first
Automated checks find only part of accessibility problems

what's inside

The original SKILL.md is organised into these sections:

When to Use
1. Establish isolated snapshots
2. Report
3. Tear down
Gotchas
Limitations

source and license

Written and maintained by @sickn33. It is published under the MIT license, which allows reuse with attribution. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.

View the full SKILL.md on GitHub ↗

Read the opening of the original SKILL.md

## When to Use

- Compare a requested page's accessibility findings between verified base and candidate revisions.
- Report introduced, fixed and still-present findings without changing application source.

## 1. Establish isolated snapshots

This package does not bundle the CLI or browser. Verify the current installed tool schema or a reviewed pinned package version first. Do not evaluate `$ARGUMENTS` or branch/URL text as shell syntax.

1. Resolve the requested base and head to full commit SHAs; identify whether staged, unstaged or untracked content belongs to the candidate.
2. Preserve the user's checkout. Prefer isolated worktrees or recoverable snapshots for base and candidate; do not switch their branch or pop an unrelated stash. A branch mode comparing only committed HEAD must disclose excluded local changes.
…

Excerpt only, quoted from the author's repository. Open the repository for the complete file.

↓ download .zip