Investigate a Sentry Error Spike

I want to investigate a Sentry Error Spike.

INSTALL (run in my terminal)
  curl -fsSL https://composio.dev/install | bash
  composio login

You have access to 1000+ app integrations through the Composio CLI.
search → find tools. execute → run them. link → connect accounts.

Workflow: search → execute. If execute fails with an auth error, run link, then retry. Don't preemptively link accounts. Bias toward action — input validation and auth errors are self-descriptive, just try it.

CORE COMMANDS

  search
    Find tools. Use this first — describe what you need in natural language.
    composio search <query> [--toolkits <slug>] [--limit <n>]

  execute
    Run a tool. Handles input validation and auth checks automatically.
    If auth is missing, the error tells you what to run.
    composio execute <slug> -d '<json>'

  link
    Connect an account. Only when execute tells you to.
    composio link <toolkit>

EXAMPLE

  composio search "create github issue"
  # → returns GITHUB_CREATE_ISSUE
  composio execute GITHUB_CREATE_ISSUE -d '{ repo: "owner/repo", title: "Bug" }'
  # → if auth missing: "Run `composio link github` first"
  composio link github
  # then retry execute

TASK: Investigate a Sentry Error Spike
Likely toolkits: Sentry, GitHub, Slack.

Steps:
  1. Fetch the Sentry issue — stack trace, frequency, users affected
  2. List recent deploys in the affected service
  3. Correlate the spike start with deploy timestamps
  4. Identify the file:line from the stack that changed in that deploy
  5. Post a heads-up in the team channel with the rollback command

Ask me before any action that sends messages or modifies data in a connected app.