dotfiles

Find commits on `master` that have not been released yet, map each author to their Slack user ID via email, and draft a Slack message pinging them for prod-release sign-off. Use when the user asks to "check unreleased commits", "ping authors before prod release", or "who hasn't signed off on the release yet" for a GitLab-hosted repo (e.g. dashboard-v4).

Conventions for building components in Aircall's UI libraries — @aircall/ds (design system, Tailwind 4 + Base UI) and @aircall/blocks (higher-level compositions) — as they live in the Aircall Hydra monorepo. Use when adding or refactoring a component in packages/ds or packages/blocks, deciding between a compound component and a prop, wiring variants, polymorphism, or exports. Triggers on "build a DS component", "add a block", or work touching packages/ds / packages/blocks inside Hydra.

Fix a broken Playwright e2e test by reproducing the failure in a real browser FIRST and capturing the live UI, then editing the test once - instead of the blind edit-rerun-repeat loop. Use when an Aircall Playwright e2e test is failing/flaky, a CI e2e job is red, or on "fix this broken test". Leans on agent-browser-aircall-local for auth + portless URLs. Guards against masking a real product regression by editing the test to pass.

Browse Aircall staging or local dev URLs with automatic authentication. USE THIS skill (not the generic agent-browser skill) whenever the target URL contains "aircall" in the hostname (e.g. dashboard.aircall-staging.com, localhost running Aircall).

Orchestrates Kento's per-ticket dev loop end-to-end: optional Jira ticket → create/reuse a git worktree → implement → debug in the browser → commit, push, open the MR → optionally watch the pipeline. Runs autonomously through setup and implementation, then STOPS at a readiness gate before shipping. Use when the user wants to start work on a ticket/feature/fix, "spin up a worktree and implement", "take this from ticket to MR", or kick off the dev flow. Delegates each step to existing skills — it does not reimplement them.

Drive a fast-forward GitLab "merge train" on Aircall repos — merge a set of approved MRs one-by-one (rebase → arm merge-when-pipeline-succeeds → poll → merge), handling approval-resets, Cursor Bugbot gates, rebase conflicts, and flaky E2E retries. Supervised, CI-paced, human-gated. Use after aircall-react-doctor-pipeline produces Ready MRs, or whenever the user asks to "watch and merge" any batch of approved MRs on an Aircall GitLab repo whose merge_method is ff. Repo-agnostic within Aircall (reads merge settings dynamically); not react-doctor-specific.

Create a GitLab merge request using glab CLI with the first commit message as the title. Use when the user asks to open an MR for the current branch targeting main, or after completing work that needs review.

Drive agent-browser against a locally-running Storybook to inspect, screenshot, and debug a single component in isolation. USE THIS skill (not the generic agent-browser skill) whenever the target is a Storybook dev server — e.g. @aircall/ds (:6008) or @aircall/blocks (:6009) in the Hydra monorepo. Renders one story via the preview iframe so the manager chrome (sidebar, toolbar, addons panel) is never in the way. Triggers on "inspect/debug a story", "screenshot a component in Storybook", or component work that needs a live render.

Attach images to a Jira issue (Jira Cloud / aircall-product.atlassian.net), optionally cropped to just a UI component instead of a full-page screenshot. Use whenever asked to "add a screenshot/image to a Jira ticket", "attach the current component to the ticket", or to put a component image in a ticket description. Covers the REST upload (the MCP/CLI can't attach), why inline-in-description embedding is impossible, and how to crop.

React performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React code to ensure optimal performance patterns. Triggers on tasks involving React components, data fetching, bundle optimization, or performance improvements.

Ping Kento on Slack (DM) when a task is fully ready / complete. Use when the user says "ping me on slack when ready/done", "slack me when this finishes", or asks to be notified on Slack after a long-running task, build, or review completes.

Browse Aircall staging or local dev URLs with automatic authentication. USE THIS skill (not the generic agent-browser skill) whenever the target URL contains "aircall" in the hostname (e.g. dev.aircall-staging.com, localhost running Aircall).

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

Helps users discover and install agent skills from the open agent skills ecosystem. Use when the user asks "how do I do X", "find a skill for X", "is there a skill that can...", or expresses interest in extending capabilities with specialized tools or workflows.

View and interact with Jira tickets using the jira CLI. Use when the user asks to view a ticket, list assigned issues, check sprint status, search issues, add comments, or change ticket status via a Jira URL or key.

Send notifications via ntfy.sh to alert about completed tasks, errors, or important events. Use when a long-running task has finished, an error needs attention, or the user explicitly asks to be notified about any event.

Opinionated constraints for building better interfaces with agents. Covers tech stack choices (Tailwind, motion/react, tw-animate-css), accessible component primitives, interaction patterns, animation guidelines, typography, layout, and performance best practices.

Design and implement web animations that feel natural and purposeful, based on Emil Kowalski's "Animations on the Web" course. Use proactively when the user asks about easing, timing, springs, transitions, animation performance, or how to animate specific UI elements. Covers CSS transitions, Framer Motion, GSAP, accessibility (prefers-reduced-motion), and common patterns like modals, tooltips, page transitions, hover states, and microinteractions.