ai-skills

Reviews JSX/TSX in a code diff for accessibility regressions. Invoked by the gate-wf workflow when .tsx/.jsx files are present.

Reviews a code diff for logic bugs, spec-code mismatches, and cross-file behavioral parity gaps. Invoked by the gate-wf workflow.

Checks reviewer findings against project context (CLAUDE.md, ADRs, Linear, PR comments, past sessions) and synthesizes findings for documented-rule violations. Invoked by the gate-wf workflow.

Reviews JSX/TSX in a code diff for i18n/l10n regressions. Invoked by the gate-wf workflow when .tsx/.jsx files plus an i18n library are present.

Reviews database migrations and bulk-update operations in a code diff for data-loss and rollback risks. Invoked by the gate-wf workflow when migration files or bulk-update APIs are present.

Use Atlassian CLI (acli) to manage Jira work items, projects, and workflows from the command line. Ideal for bulk operations, automation, scripting, and when users request CLI-based Jira interactions. Trigger on requests like "use Jira CLI", "create Jira issues via CLI", "bulk update Jira tickets", "automate Jira workflows", or when users want to script Jira operations.

This skill should be used when implementing code that requires SOLID principles and clean code practices. It provides detailed guidance on Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion principles with comparison examples in TypeScript.

Specialist for TypeScript backend development including Node.js servers, NestJS applications, APIs, databases (PostgreSQL, MongoDB, Redis), authentication, testing, deployment, server-side code, microservices, database queries, migrations, controllers, services, repositories, and middleware. Use for ANY work involving .ts backend files, server-side architecture, performance optimization, and backend security.

This skill should be used when the user wants to write their end-of-day / evening "build-in-public" update for a given Linear project — 3-4 impact-focused bullets plus a Next line synthesized from the project's Linear activity and the repo's git/PR shipping evidence, ready to paste into the pod thread. Invoke as /build-in-public with a Linear project ID. Triggers on "build-in-public post", "evening update", "what did I ship today", "end-of-day update", or any variant of "what did I do today" for a work update — even without the word "skill". Default to drafting; never post anywhere automatically.

Interact with a local Chrome browser session via Chrome DevTools Protocol (only on explicit user approval after being asked to inspect, debug, or interact with a page open in Chrome). Pass `--isolated` to drive a sandboxed Chrome with a dedicated profile instead of the user's real browser.