Skip to content
Skills Library
DevOps & cloud · Building & coding

fix

/fix

Fix what is broken in the user's live app using Vigilia. Finds the worst open incident (or the one named), reads Vigilia's plain-language diagnosis, evidence and fix prompt, fixes the cause in this codebase, and hands it back to Vigilia to verify with real traffic. Use when the user asks to fix Vigilia incidents, asks what is broken in production, or pastes a Vigilia incident id or link. Examples: \"fix my Vigilia incidents\", \"what's broken in prod?\", \"fix incident abc123\", \"Vigilia emailed me about checkout — fix it\".

Licence
MIT
Last repository change
30.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Fix what is broken in the user's live app using Vigilia. Finds the worst open incident (or the one named), reads Vigilia's plain-language diagnosis, evidence and fix prompt, fixes the cause in this codebase, and hands it back to Vigilia to verify with real traffic. Use when the user asks to fix Vigilia incidents, asks what is broken in production, or pastes a Vigilia incident id or link. Examples: \"fix my Vigilia incidents\", \"what's broken in prod?\", \"fix incident abc123\", \"Vigilia emailed me about checkout — fix it\".

Triggers from the description

fix my Vigilia incidents\what, \
Original author description

Fix what is broken in the user's live app using Vigilia. Finds the worst open incident (or the one named), reads Vigilia's plain-language diagnosis, evidence and fix prompt, fixes the cause in this codebase, and hands it back to Vigilia to verify with real traffic. Use when the user asks to fix Vigilia incidents, asks what is broken in production, or pastes a Vigilia incident id or link. Examples: \"fix my Vigilia incidents\", \"what's broken in prod?\", \"fix incident abc123\", \"Vigilia emailed me about checkout — fix it\".

How it works

  1. Before you start
  2. 1. Pick the incident
  3. 2. Read it
  4. 3. Find the cause
  5. 4. Fix it
  6. 5. Hand it back
Original SKILL.md headings · 59 lines, 658 words
SKILL.md preview
---
name: fix
description: "Fix what is broken in the user's live app using Vigilia. Finds the worst open incident (or the one named), reads Vigilia's plain-language diagnosis, evidence and fix prompt, fixes the cause in this codebase, and hands it back to Vigilia to verify with real traffic. Use when the user asks to fix Vigilia incidents, asks what is broken in production, or pastes a Vigilia incident id or link. Examples: \"fix my Vigilia incidents\", \"what's broken in prod?\", \"fix incident abc123\", \"Vigilia emailed me about checkout — fix it\"."
---

# Fix a Vigilia incident

Vigilia watches this person's live app. Its MCP tools (server `vigilia`) give you the diagnosis and the evidence for each problem. Your job is to fix the cause in this codebase and hand the incident back to Vigilia, which then confirms with real traffic whether the fix held.

## Before you start

This needs Vigilia's tools (`list_open_incidents`, `get_incident`, `mark_fixed`), which come from Vigilia's MCP server. If they aren't available, Vigilia isn't signed in yet. Don't look for config files, tokens or other servers. Tell the user:

> Vigilia isn't connected yet. Connect its MCP server in your agent's settings (`https://app.getvigilia.com/mcp`), sign in on the Vigilia page that opens and choose **Allow**. Then ask me again.

Then stop.

## 1. Pick the incident

- If an incident id or a Vigilia incident link was given, use that id. A link ends in `/incidents/<id>`.
- Otherwise call `list_open_incidents` and take the first one. It is sorted worst first. If several apps are listed and the one this repo builds is obvious, use `list_open_incidents` with that `appId`.
- Tell the user in one line which incident you're taking and why.

If there are no open incidents, say so and stop. Don't go looking for problems Vigilia didn't report.

## 2. Read it

Call `get_incident`. Read all of it before touching code:

- **What's broken / who's affected**: the symptom, in the user's words.
- **Evidence**: the error message, the page the visitor was on, and, for a failed request, the endpoint that failed. Also the stack frames, and what the visitor did right before.
- **Vigilia's fix prompt**: a strong lead written by a model that never saw this code. Verify it against the code instead of applying it blindly.

Two details in the evidence are easy to misread:

- The page is where the visitor was standing, not necessarily where the fault is. For a failed request, the fault is at the request target.
- `HTTP 0` means the request never completed. That is network-level, not an application bug.

## 3. Find the cause

- Search for the stack frames' file and function names first. Minified frames still carry component names and string literals.
- For a failed request, find where the app calls that endpoint, and whether this repo also serves it.
- If the fault is outside this repo (a third-party API that is down, a backend in another repo, a database rule such as a Supabase RLS policy), say so plainly. Fix what is fixable here, such as handling the failure gracefully, and tell the user what must change elsewhere.
- If the evidence contradicts the diagnosis, trust the evidence and tell the user.

## 4. Fix it

- Make the smallest change that removes the cause. Don't refactor unrelated code.
- The fix should also leave the user-facing behaviour sane: a visitor should see a helpful message, not a frozen screen.
- If the project has tests, add a regression test that fails without the fix and passes with it.
- Run the project's own checks (typecheck, lint, tests) where they exist.

## 5. Hand it back

- Explain in plain language what broke, what you changed, and how to see that it works. The user may not read code.
- Vigilia's verification only means something once real visitors run the new code. Call `mark_fixed` **after the fix is deployed**:
  - If the user deploys by pushing (Vercel, Netlify, Lovable…) and asked you to commit and push, push first, then call `mark_fixed`.
  - Otherwise ask: "Once this is deployed, shall I mark it fixed in Vigilia so it can confirm with real traffic?"
- If several open incidents share this root cause, mark each of them fixed.
- Afterwards, `get_fix_status` tells whether the fix held. After about a day of traffic it reads confirmed; if the error comes back, the incident reopens.

Never print, log or commit the Vigilia API token.

Versions

RepositoryScoreLicence
This page · getvigilia/vigilia-agent-plugins90MIT
swingerman/engineer100MIT
Hainrixz/claude-seo-ai100MIT
vanducng/skills100MIT
RemiPelloux/kill-my-idea100MIT
tony/skills100MIT
applelog/nondev-kit100MIT
A7-studio/jobmigo100MIT
koda-ai-studio/agent-bom100Apache-2.0

Database snapshot: 13.11.2026 · package version e9f731a5806b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90install
    Install Vigilia error monitoring in this project. Adds the Vigilia script tag in the right place for the framework, allows it in an existing Content-Security-Policy (never adds one or loosens it), and verifies the live install. Use when the user asks to add, install or set up…
  • 100vigil-incident
    Incident response — diagnose production issues, find root cause, propose fix with rollback. Use when asked about "something is broken", "production issue", "why is this down", "incident", or "debug production".
  • 95glab-incident
    Manage GitLab incidents for issue tracking and incident management. Use when creating incidents, managing incident response, or linking incidents to issues. Triggers on incident, incident management, create incident, incident response.
  • 100incident
    Triage a production bug or incident report (log, error, tracker URL, user complaint) without touching production. Classify severity, route to /debug, /fix, /rollback, or /feature, and write an incident record. Use for /incident, production is broken, user reports an error, or…
  • 100incident-response
    Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan…
  • 100incident-response
    Run a structured incident response. Use when the user says "we have an incident", "production is down", "service is degraded", "on-call response", "p0 incident", "something is broken in prod", "help me manage this incident", "incident commander", or there is an active production…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.