trigger-dev

Plugin trigger-dev from marketplace plugin-trigger-dev in yigitkonur/plugin-trigger-dev. Commands read from the repo's manifest — 11 days ago.

Skills (7)

• audit

  Review a Trigger.dev codebase against the plugin's rule catalog (stale APIs, silent-failure patterns, config, deploy, cost) and write a findings report; optionally apply safe fixes.

• chat-agent

  Build, migrate or debug AI chat agents on Trigger.dev (chat.agent, the chat transport, sessions, transcript storage, tool approvals, server, Slack and Linear callers). Use when a Trigger.dev project needs a chat assistant or agent, or code imports @trigger.dev/sdk/ai or @trigger.dev/sdk/chat.

• diagnose

  Find out why Trigger.dev runs or deploys misbehave (stuck QUEUED or PENDING_VERSION, failed, timed out, crashed or OOM, schedules not firing, 429s, CI deploy failures, chat history lost). Use when a Trigger.dev project shows an error, a run id such as run_abc123, or the user says a task did not run.

• doctor

  Check the Trigger.dev toolchain around this project (Node, CLI login and profile, MCP server, versions, duplicate official skills, self-host target, plugin install scope) and report what to fix.

• init

  Set up Trigger.dev in this repository with a short discovery, an explicit architecture decision, and a first task proven to run.

• new

  Add one capability to an existing Trigger.dev project (a task, a schedule, a progress UI, an approval step, a webhook handler) and prove it runs.

• ship

  Deploy Trigger.dev tasks (trigger deploy) to staging, prod or a preview branch with a preflight, the right CI or integration pipeline, an explicit --env, and a verification step. Use when asked to deploy, ship or release the Trigger.dev tasks or jobs. Not for deploying the app itself to Vercel, Fly

Subagents (2)

• code-auditor

  Judges located Trigger.dev rule hits in one audit domain (tasks, realtime, chat, config, deploy, cost) by reading the code, drops false positives, and returns findings as JSON. Use from the audit command, one instance per domain.

• run-investigator

  Investigates Trigger.dev runs, queues and deployments with live MCP data and returns a short verdict with evidence. Use for a run id, a failing task, stuck queues, or whether prod is healthy. Read-only (it has no file-edit or MCP write tools).

MCP servers (1)

• trigger

  runs: npx trigger.dev@latest mcp

Hooks (18)

• SessionStart

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"

• PostToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/marker-gate.sh" lint --hook

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/marker-gate.sh" guard --alias

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/marker-gate.sh" guard --alias

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/marker-gate.sh" guard --alias

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/marker-gate.sh" guard --alias

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

Similar plugins