a11y-pass
Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.
$ npx -y skills add Archive228/loopkit --skill changelog-from-diff --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/changelog-from-diffContext preview
The summary Claude sees to decide when to auto-load this skill.
Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.
name: changelog-from-diff description: Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description. when_to_use: cutting a release, writing release notes, summarizing a branch
Read the actual diff/commits, not the commit messages (they lie). Group into: **Added · Changed · Fixed · Removed · Security** (skip empty groups). Each line: user-facing impact, not implementation. "Fixed login failing for emails with uppercase characters" — not "fixed bug in user lookup".
Output: markdown ready to paste. If a change has no user impact, leave it out.
33 battle-tested skills + minimal .claude harness for any coding agent (Claude Code, Cursor, Codex, Gemini CLI).
Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable). Read it alongside claude-progress.txt…
Review a diff against the goal spec assuming the code is BROKEN. The reviewer
Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything…