amineorion
UserProduction-safety skills for Claude Code — stop AI agents from breaking prod, leaking tenant data, or shipping CVEs. From palaheal.dev.
Categories
Indexed Skills (5)
cross-tenant-leak-reviewer
Review the current diff for cross-tenant data leaks and irreversible operations before merge, with fresh eyes and no implementation bias. Use before committing or opening a PR on a multi-tenant SaaS, when the user asks to review a change for tenant safety, or after writing data-access, cache, job, or migration code.
harden
Install the always-on safety hooks (destructive-command-guard + tenant-scope-guard) into this project. Use when setting up a multi-tenant or production codebase for agent-authored changes, or when the user asks to "harden", "add safety hooks", or "guard prod".
migration-safety-check
Review a database migration for safety before it runs against a multi-tenant production database, where one bad migration hits every customer at once. Use when the user writes, edits, or is about to run a migration, or asks whether a schema change is safe.
tenant-scope-audit
Audit a multi-tenant codebase for queries, caches, jobs, or searches that are missing a tenant filter — the missed WHERE tenant_id that becomes a cross-tenant data leak. Use whenever the user works on a multi-tenant SaaS, asks to check tenant isolation, reviews data-access code, or mentions tenant scoping, RLS, or data leaks.
two-tenant-verify
Verify tenant isolation by exercising a data change as a second tenant and confirming the first tenant's data is invisible — in the running app, not just tests. Use after changing data-access code on a multi-tenant SaaS, before merging, or when the user asks to prove isolation holds or test for leaks end to end.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.