Archive228/loopkit - Page 2

design-system

Make frontend output look intentional, not AI-generated. Use for any UI work — components, pages, layouts.

flaky-hunter

Diagnose and fix tests that pass sometimes and fail other times. Use when CI is red intermittently.

kill-dead-code

Find and remove unreachable/unused code safely. Use during cleanup or before a refactor.

migration-writer

Write safe, reversible database migrations for this repo's conventions. Use for any schema change.

owasp-review

Security-review a diff against the OWASP Top 10. Use before merging anything that touches auth, input handling, queries, or external calls.

pr-from-diff

Write a PR description a reviewer can approve fast. Use when opening any pull request.

readme-audit

Check whether a README actually lets a stranger run the project. Use on any repo's README before publishing.

rebase-safely

Rebase, squash, or rewrite history without losing work or breaking shared branches. Use before any history rewrite.

schema-diff

Compare two schema states and surface the risky changes. Use before applying migrations or after a model change.

secret-scan

Catch hardcoded secrets, keys, and tokens before they get committed. Use before any commit and on any file with credentials.

simplify

Reduce a change to the minimum that solves the problem. Use when code is over-engineered or a diff is bloated.

sql-review

Review SQL and ORM queries for correctness, safety, and performance before they ship.

systematic-debugging

Use for ANY bug, test failure, crash, or unexpected behavior. Forces reproduce-then-isolate before proposing a fix. Stops the agent from guessing.

write-failing-test-first

Before fixing any bug, write a test that reproduces it and watch it fail. Use for every bug fix.