メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ping-me-slack |
| description | 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. |
Send a Slack DM to Kento when work is fully ready — task complete, build green, PR mergeable, review done. This is the "I'm finished, come look" signal.
| Field | Value | Notes |
|---|---|---|
| Channel ID | D02HB6U23N0 | Kento's DM (Slackbot/self DM). IDs starting with D are direct messages. |
Source: https://aircall.slack.com/archives/D02HB6U23N0
mcp__claude_ai_Slack__*) must be authenticated. If a call fails
with an auth error, run mcp__claude_ai_Slack__authenticate first, then retry.Only ping when the work is genuinely done and verified — not at the start, not mid-progress. "Fully ready" means:
If the task ended in failure or is blocked, still ping — but say so clearly so the user knows it needs attention rather than expecting success.
One line, scannable on a phone lock screen. Lead with a status glyph:
✅ — done and verified⚠️ — done but with caveats / needs a look❌ — failed or blocked, needs attentionInclude the concrete result, not just "done":
✅ release-ping skill created — tests 12/12 green, ready to merge⚠️ migration applied — 1 row skipped, check logs❌ build failed — TS error in src/index.ts:42mcp__claude_ai_Slack__slack_send_message(
channel_id: "D02HB6U23N0",
message: "<status line>"
)
Report back the message_ts so the user knows it landed, and so a follow-up
can be threaded with thread_ts if needed.
notify — lighter-weight ntfy.sh push when a Slack DM is overkill.release-ping-dashboard — pings other people (commit authors) for sign-off,
using the same Slack MCP.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.