.agents/skills/observability-sentry-logging/SKILL.md
# Skill: observability-sentry-logging ## Purpose Add logging and error tracking with safe redaction. ## Triggers - Adding API routes - Implementing billing - Admin write operations ## Canonical References - AGENTS.md (No sensitive logs) ## Responsibilities - Structured logs - Redact tokens - Add request-id ## Implementation Steps 1. Add logger utility. 2. Mask sensitive fields. 3. Integrate Sentry (if used). 4. Attach request-id per request. ## Required Artifacts - packages/observability/*
npx skillsauth add jang4360/historychat .agents/skills/observability-sentry-loggingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Add logging and error tracking with safe redaction.
development
# Skill: testing-vitest-playwright ## Purpose Ensure test coverage for route handlers and critical flows. ## Triggers - New API route - Billing logic - Auth changes ## Responsibilities - Unit test core logic - Test webhook idempotency - Test auth guards ## Implementation Steps 1. Write unit test for business logic. 2. Mock webhook replay scenario. 3. Test unauthorized access case. ## Required Artifacts - tests/*
development
# Skill: systematic-debugging ## Purpose Enforce structured debugging workflow. ## Triggers - Production bug - CI failure - Billing mismatch ## Responsibilities - Reproduce - Identify root cause - Patch - Add regression test ## Implementation Steps 1. Reproduce issue locally. 2. Add failing test. 3. Fix. 4. Confirm test passes.
testing
# Skill: supabase-rls-standard ## Purpose Apply standardized Row-Level Security policies. ## Triggers - Creating new tables - Modifying ownership rules - Introducing role-based access ## Canonical References - SECURITY_CHECKLIST.md (RLS section) - AGENTS.md ## Responsibilities - Ensure RLS is enabled - Apply ownership + role override template - Index policy columns ## Implementation Steps 1. Enable RLS on new tables. 2. Create SELECT/INSERT/UPDATE/DELETE policies. 3. Use ownership pattern:
tools
# Skill: supabase-auth-ssr-session ## Purpose Implement SSR-based authentication using Supabase with secure cookie handling. ## Triggers - Adding login/logout - Protecting routes - Accessing user session server-side ## Canonical References - AGENTS.md - SECURITY_CHECKLIST.md (Auth section) ## Responsibilities - Create browser and server Supabase clients - Enforce cookie-based session flow - Protect admin routes ## Implementation Steps 1. Create `createBrowserClient` and `createServerClient`