Resolve AI

Skills

• alerts

  List and filter alerts in Resolve. Use when the user asks "show me alerts", "any new alerts", "alerts on <team>", "find the alert matching <pattern>", "alerts that auto-investigated", "alerts where <label> is critical/missing", or wants a focused alerts view (separate from a full overview snapshot).

• apply-fix

  Turn a Resolve investigation's root-cause findings into code changes in your local repo. Use when the user wants to translate findings into code changes — phrases like "fix this based on Resolve", "implement Resolve's mitigation", "apply the fix from this investigation", "remediate the root cause Resolve found", or wants to write code to address a theory Resolve identified.

• ask

  Send Resolve a question or a request to investigate — continuing an existing chat or investigation, or starting a fresh one. Use when the user wants to send a message to Resolve — phrases like "ask Resolve about X", "follow up with Resolve", "what does Resolve think about Y", "have Resolve check Z", or wants Resolve to clarify a finding.

• chats

  List recent Resolve chats. Use when the user asks "show me my chats", "what chats are in flight", "any chats running", "chats from last week", or wants a focused chat list (separate from a full overview snapshot).

• create-skill

  Write or tune a skill for the Resolve plugin — encoding workflow guidance, not tool API details.

• demo

  Run a guided, self-paced tour of Resolve using the connected org's live data — surface the environment, resume a chat, fire several in parallel, drill a real RCA with its evidence and a live thread, then investigate something from scratch. Use when someone wants to demo Resolve, give a tour, or show a new user what it can do — phrases like "demo Resolve", "give me a tour", "walk them through Resolve", "show me what Resolve can do", "demo this to <person>".

• feedback

  Send Resolve your feedback — on an investigation's root cause, a chat answer, or the Resolve experience itself. Use when you've resolved or mitigated your issue, an investigation or chat wraps up, or you want to rate or comment on Resolve.

• help-resolve

  Introduce Resolve (the AI DevOps investigation platform) and route the user to the right next step — investigate, ask, apply a fix, or get an overview. Use when the user mentions "Resolve", "resolve.ai", asks "what is Resolve" or "how do I use Resolve", pastes a Resolve URL, or describes a production incident or active investigation they want Resolve to help with.

• investigate

  Have Resolve run a root-cause investigation — open an existing canvas, or start a new one. Use when the user pastes a Resolve URL, names an investigation ID, references an alert, or describes a problem — phrases like "investigate X", "look into Y", "have Resolve check Z", "start an investigation", "rca this", or "root cause this".

• investigations

  List recent Resolve investigations. Use when the user asks "show me investigations", "list my team's investigations", "investigations from last week", "what auto-investigations ran today", "any manual investigations this month", or wants a focused investigations view (separate from a full overview snapshot).

• overview

  Get the big-picture view across all of Resolve — open investigations, recent alerts, in-flight chats. Not for the status of a single investigation or chat.

• prod-context

  Get production context from Resolve for the area you're about to change — so the work is grounded in what production looks like and aware of how the change could affect it, before you start rather than after the PR is up. Use before implementing a fix or feature, when finalizing a plan or approach, or before editing anything that affects a production system — application code, infrastructure, or config-as-code (Helm, Terraform, Dockerfiles, CI/CD, SQL/migrations, protos) — or when the user says "let's build/fix/implement X". Surfaces the area's normal operational profile (traffic and usage, telemetry coverage, baseline latency/error rate), the regression risk of the change, plus any active alerts, open investigations, recent incidents or deploys, and known fragility.