Debug & triage
5,150 rows, by stacks then stars
1,113 of these skill files have been read, by 1,020 distinct authors, and what they tell an agent counted. What Debug & triage authors agree on, and what they forbid
TeoSlayer/pilot-skills/skills/pilot-event-replay Skill
9★ repoRecord and replay event streams for debugging, testing, and audit purposes. Use this skill when: 1. You need to capture event streams for later analysis 2. You need to replay events to test downstream consumers 3. You need to debug event-driven workflows 4. You need to audit event history with timestamps Do NOT use this skill when: - You need real-time event forwarding (use pilot-event-bus instead) - You need long-term storage with rotation (use pilot-event-log instead) - You need filtering before recording (use pilot-event-filter first)
TeoSlayer/pilot-skills/skills/pilot-healthcare-triage-setup Skill
9★ repoDeploy a healthcare triage system with 4 agents for patient intake, symptom analysis, appointment scheduling, and HIPAA-compliant records. Use this skill when: 1. User wants to set up a healthcare triage or patient routing system 2. User is configuring an agent as part of a medical intake workflow 3. User asks about symptom analysis, appointment scheduling, or HIPAA-compliant record keeping Do NOT use this skill when: - User wants a simple chat interface (use pilot-chat instead) - User wants to log a single audit event (use pilot-audit-log instead)
TeoSlayer/pilot-skills/skills/pilot-log-analytics-setup Skill
9★ repoDeploy a log analytics system with 4 agents for collection, parsing, alerting, and visualization. Use this skill when: 1. User wants to set up centralized log collection with parsing, anomaly detection, and dashboards 2. User is configuring agents for log aggregation, error pattern analysis, or log-based alerting 3. User asks about log pipelines, anomaly detection on logs, or log visualization across agents Do NOT use this skill when: - User wants to stream a single data feed (use pilot-stream-data instead) - User wants to set a one-off alert (use pilot-alert instead) - User only needs event filtering (use pilot-event-filter instead)
emaraschio/cursor-commands/.cursor/skill-contracts/add-error-handling Skill
9★ repoAdd consistent error handling to the targeted code
emaraschio/cursor-commands/.cursor/skill-contracts/debug-issue Skill
9★ repoSystematically debug a reported issue
emaraschio/cursor-commands/.cursor/skill-contracts/prompt-eval-debug Skill
9★ repoDebug and improve any prompt without rewriting blindly. Builds a tiny eval suite (control, edge, capability-boundary cases), diagnoses failures as prompt issue, missing tool or capability, or harness/workflow issue, and proposes the smallest next change. Use for prompt debugger, eval suite, improve prompt, or before editing catalog eval/cases.md.
emaraschio/cursor-commands/plugin/.cursor/skill-contracts/add-error-handling Skill
9★ repoAdd consistent error handling to the targeted code
emaraschio/cursor-commands/plugin/.cursor/skill-contracts/debug-issue Skill
9★ repoSystematically debug a reported issue
emaraschio/cursor-commands/plugin/.cursor/skill-contracts/prompt-eval-debug Skill
9★ repoDebug and improve any prompt without rewriting blindly. Builds a tiny eval suite (control, edge, capability-boundary cases), diagnoses failures as prompt issue, missing tool or capability, or harness/workflow issue, and proposes the smallest next change. Use for prompt debugger, eval suite, improve prompt, or before editing catalog eval/cases.md.
SanderMoon/local-brain/pkg/skillscatalog/skills/brain-triage Skill
9★ repoProcess inbox items systematically — refile to projects, add metadata, or discard. Use when the inbox has items, after a daily briefing reveals pending captures, or when the user says "process my inbox", "triage", or "clean up my dump".
psenger/ai-agent-skills/.claude/skills/start Skill
9★ repoBegins a new piece of work in the ai-agent-skills repository. Two modes: EXISTING ISSUE (user provides a GitHub issue number or URL — fetches it, cuts the correct branch) and NEW ISSUE (user describes what needs doing — classifies as feature or bug, drafts a structured requirement using the repo's issue template, confirms with the user, creates the GitHub issue, then cuts the branch). Always checks GitHub auth first and confirms user identity. Use when the user says "start work on #14", "begin issue", "start a new feature", "I need to build X", "create an issue for Y", or passes a GitHub issue URL. Load the `conventions` skill for branch naming rules.
QBall-Inc/the-bulwark/skills/issue-debugging Skill
8★ repoSystematic methodology for issue debugging including root cause analysis, impact mapping, tiered validation plans, and confidence assessment. Use when analyzing bugs, fixing issues, or validating fixes.
aakashdhar/vibe-skill/vibe-fix-bug Skill
no license8★ repoFull spec-driven workflow for diagnosing and fixing a bug with an AI coding agent. Triggers on "bug:" prefix, "I have a bug", "something is broken", "this is not working", "fix this issue", "there is a bug in", "debug this", "broken", "issue". Always use when the user reports unexpected behaviour — even without the exact prefix. Three-way severity triage: trivial bugs (3 tasks, no folder), environment bugs (runs vibe-doctor first, no BUG_SPEC), significant bugs (full workflow). Environment bugs — HMR loops, missing deps, config mismatches, build tool failures — are detected at triage and routed to vibe-doctor rather than full bug workflow. Diagnosis always before the fix. Regression test always before fix code. BUG_SPEC.md, BUG_PLAN.md, BUG_TASKS.md created for significant bugs only.
1Mangesh1/hipaa-guardian/skills/hipaa-guardian Skill
8★ repoThis skill should be used when the user asks to "scan for PHI", "detect PII", "HIPAA compliance check", "audit for protected health information", "find sensitive healthcare data", "generate HIPAA audit report", "check code for PHI leakage", "scan logs for PHI", "check authentication on PHI endpoints", "scan FHIR resources", "check HL7 messages", or mentions PHI detection, HIPAA compliance, healthcare data privacy, medical record security, logging PHI violations, authentication checks for health data, or healthcare data formats (FHIR, HL7, CDA).
JasonWarrenUK/goblin-mode/skills/role-expert-debug_dervish Skill
no license8★ repoSystematic debugging methodology — runtime errors, test failures, logic bugs, performance issues, production incidents. Five-step framework, root-cause analysis, browser/Node/Svelte tooling, and common bug patterns.
hamza-ali-shahjahan/hamzaish/_archive/v0/agents/scale/support-triage Skill
8★ repoTriage incoming support — categorize, prioritize, draft responses, identify product bug vs user-error vs feature-request. Routes to engineering when needed.
hamza-ali-shahjahan/hamzaish/factory/agents/scale/support-triage Skill
8★ repoTriage incoming support — categorize, prioritize, draft responses, identify product bug vs user-error vs feature-request. Routes to engineering when needed.
hamza-ali-shahjahan/hamzaish/factory/skills/debugging-and-error-recovery Skill
8★ repoGuides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
The same file is in 127 other repositories
dayfinggg/claude-code-codex-skills/claude/skills/diagnosing-bugs Skill
8★ repoDiagnose and fix difficult defects, regressions, intermittent failures, crashes, and performance problems through a reproducible evidence loop. Use when software is broken, failing, flaky, unexpectedly slow, or when the user asks to debug, diagnose, find a root cause, or repair a non-obvious bug. Do not use for obvious local corrections, feature development without a defect, or speculative architecture review.
vanducng/skills/skills/debug Skill
8★ repoDebug systematically across software, data pipelines, infrastructure, and analytics. Find root cause and produce verified evidence - for bugs, test failures, CI/CD breakage, K8s/Cloud incidents, dbt/Airflow pipeline failures, schema drift, freshness violations, dashboard wrong-numbers, and performance issues. Diagnoses and hands the fix to vd:fix; validates at every layer and verifies with fresh evidence before claiming a cause.
narrative-io/narrative-skills-marketplace/plugins/narrative-identity/skills/triage-pregraph-data Skill
8★ repoAudit a dataset or access rule before it joins an identity-graph build (access rules behave like datasets in NQL here). Enumerates failure modes (hub identifiers, high-degree nodes, suspicious values, over-connected identifiers), tests hypotheses in parallel, quantifies damage by rows / edges / entities, and proposes minimal filters ranked by severity. When issues are found, returns a validated `CREATE MATERIALIZED VIEW` NQL the caller can run to produce a graph-ready clean source; if the data passes, says so and recommends it unchanged. Plans and authors the clean-view NQL; does not execute it. Use when: "audit this dataset before the graph build", "find bad edges in <source>", "check identity data quality", "recommend filters for the graph build", "quantify damage from <identifier_type>", "pre-graph DQ". (narrative-identity)
kensaurus/cursor-kenji/skills/audit-resilience Skill
8★ repoRead-only audit for the non-functional "20%" AI agents systematically skip: timeouts, retries with backoff+jitter, circuit breakers, idempotency keys, rate limiting, graceful degradation/fallbacks, cancellation, audit logging on sensitive actions, and PII handling in logs. Inventories every external call, mutation, webhook, and payment path and marks each concern Implemented/Partial/Missing with file:line, severity, and the exact skill to fix it. Use when "is this production-ready", "resilience audit", "will this survive real traffic", "audit retries/timeouts/idempotency", "reliability review", "the 80% problem", or "audit-resilience". Produces a prioritized report only — remediation is delegated to backend-error-handling / backend-observability / backend-patterns / plan-* skills.
kensaurus/cursor-kenji/skills/backend-error-handling Skill
8★ repoImplement solid error handling patterns. Use when adding error handling, improving error UX, debugging error flows, standardizing error responses, or when user mentions "error boundary", "try/catch", "error state", "toast notification", "form validation error", or "API error handling".
kensaurus/cursor-kenji/skills/backend-observability Skill
8★ repoInstrument features so errors, traces, and logs are correlated from the first line. Use when adding logging, tracing, or monitoring; wiring Sentry, Langfuse, or structured logs; or when asked "add logging", "instrument this", "why can't I debug prod", "correlate the error to the trace", "redact PII from logs", "set up alerts/SLOs".
kensaurus/cursor-kenji/skills/debug-error Skill
8★ repoSystematic debugging workflow for errors and bugs. Use when debugging errors, investigating bugs, troubleshooting issues, or when something isn't working as expected. Integrates Sentry MCP for production error context, Firecrawl for researching fix patterns, and Sequential Thinking for complex multi-step diagnosis.
kensaurus/cursor-kenji/skills/debug-fe-be-integration Skill
8★ repoDebug frontend-backend integration issues for any project by analyzing backend logs, identifying incorrect API calls, and fixing both sides. Auto-detects FE/BE frameworks, API style (REST/GraphQL/tRPC), and validation library. Uses Sentry MCP for production error context, Firecrawl for debugging pattern research, and Supabase MCP for data verification. Replaces hardcoded paths with auto-detected patterns. Use when diagnosing API errors, mismatched requests, integration issues between frontend and backend, or when the user mentions API 4xx/5xx errors, validation failures, or FE-BE contract mismatches.
kensaurus/cursor-kenji/skills/debug-sentry-monitor Skill
8★ repoMonitor, triage, fix, and proactively enhance Sentry error monitoring for any project. Use when asked to: check Sentry, fix Sentry errors, triage Sentry issues, run post-deploy monitoring, review production errors, clean up Sentry noise, audit Sentry setup, improve monitoring coverage, enhance error tracking, or "run sentry check". Works with any GitHub repo — auto-detects org, project, framework, and config. Fetches issues via Sentry MCP, triages them, performs root cause analysis, fixes code bugs, updates noise filters, audits the monitoring architecture, and resolves issues only after verified fixes.
kensaurus/cursor-kenji/skills/mobile-emulator-start Skill
8★ repoBoots a clean Android emulator + Metro (Expo dev-client / bare React Native) with the right ordering: inspect existing IDE terminals first, kill stale ports/processes, choose "fresh cache wipe" vs "fast iteration" for Hot Reload, default to **1080×2400** display (standard phone size; use a tall 1080×4000 display only when scroll-QA is requested and a matching tall skin is applied), adb reverse + poll Metro /status before deeplink to avoid connection races, and troubleshoot adb/Expo connectivity and white-screen. Use when asked to start Metro and emulator, restart dev loop, fix “Cannot connect to Expo”, spin up a new terminal instance, debug stuck bundler, or align emulator geometry for scroll QA. Generic for any app; repos may wrap these steps in package.json scripts.
kensaurus/cursor-kenji/skills/plan-error-handling Skill
8★ repoAudit a codebase for silent failures, swallowed exceptions, and observability gaps across Sentry and Langfuse, then produce a phased fix plan. Use when the user says "errors aren't showing in Sentry", "things fail silently", "empty catch blocks", "add error handling", "check my Langfuse tracing", or is hardening observability before launch. Covers error handling and LLM observability (untraced model calls, missing cost/latency, no eval scores). Plan only until each phase is approved. Pairs with backend-observability, debug-sentry-monitor, audit-langfuse-llm. Do NOT use for live incidents (debug-error).
kensaurus/cursor-kenji/skills/test-playwright Skill
8★ repoClose the PDCA loop on the work you just did. After implementing changes, drive the LIVE app on localhost through the Playwright browser MCP like a real end user — manually, in a visible (headed) browser, clicking and typing one action at a time, NEVER through scripts or test runners — exercising every page, component, and flow the current session touched. Reproduce real user journeys, hunt for pain points, and FIX them as you go (full-stack: UI/UX + backend + DB), using already-enabled MCP servers (Sentry for production errors, Supabase for schema/logs/data, Firecrawl for research). Red-team your own work, give brutally honest critique, and suggest feature/UX improvements. Generic across any repo and stack. Use after building or changing a feature, or when the user says "test this with playwright", "test my changes", "test on localhost like a user", "PDCA this", "did you actually test it", "red-team this feature", or "verify the work end-to-end".
kensaurus/cursor-kenji/skills/test-red-team Skill
8★ repoAdversarial red-team of a running web, React Native, or Capacitor hybrid app. Drives a visible (headed) browser by hand — Playwright browser MCP (web/PWA), Android WebView attach (Capacitor), or adb tap-walk (native) — never scripted test files. Attacks every feature across 4 dimensions: UI/UX, data pipeline, security (OWASP-mapped), and performance. Cross-references Sentry telemetry, Supabase DB-layer mutation truth and RLS, and current OWASP/MASVS guidance. Produces a severity-ranked defect list with repro steps and evidence. Generic across any repo and stack. Use when asked to "red team this app", "attack my app", "break it", "find all the defects", "adversarial test", "pre-launch hardening", "pentest the app", or "full app QA". Distinct from test-playwright (session PDCA), test-qa (happy-path crawl), and audit-security (static code review).
kensaurus/cursor-kenji/skills/workflow-fix-and-ship Skill
8★ repoComplete bug-fix lifecycle in one sweep: triage production signals (Sentry / logs) → reproduce → fix (debug-error) → verify full-stack (test-playwright) → PR (workflow-pr) → post-deploy smoke (deploy-verify). Use when "fix this bug and close the ticket", "patch this and ship", "fix this Sentry issue", "bug report from user", or when a production error needs to go from alert to resolved in a single session.
0xMassi/claude-skills/go-strict Skill
8★ repoGo coding standards, clean code, and security rules. Use when writing, reviewing, or refactoring Go code. Covers error handling (wrapping with %w), package organization (internal/pkg split), concurrency safety (sync.RWMutex, goroutine lifecycle), Gin handler patterns, input validation, structured logging with zerolog, graceful shutdown, and naming conventions. Derived from production Go services.
matematicsolutions/awesome-matematic-skills-pl/governance-kancelarii/skills/ai-act-triage-pl Skill
8★ repoPolish hub of legal-AI skills - 41 skills in 8 Claude Code / Cowork bundles (LLM output verification, PL/EU case law, DOCX redline, AI Act audit bundle). GDPR-safe, vendor-neutral, MIT.
stark-ai-de/agent-skills/incubator/skills/repo-maintenance/ci-debugger Skill
8★ repoDiagnose failed CI jobs and build pipelines using small-log, evidence-first debugging. Use when the user shares a failed GitHub Actions, GitLab CI, Vercel, or package-manager build and wants root cause, minimal fix, and regression test guidance.
stark-ai-de/agent-skills/incubator/skills/repo-maintenance/issue-triage Skill
8★ repoTriage repository issues through a maintainer decision tree. Use when the user asks to classify issues, apply labels, identify missing information, mark ready-for-agent work, split vague reports, or clean up an issue inbox.
quivly/skills/customer-engineering/inbox-triage Skill
8★ repoAnswers "what needs my attention today" across a CSM's book of business — new risk signals, health drops, upcoming renewals, and accounts going quiet, ranked by urgency. Use at the start of the day or week, or when asked "what should I focus on".
Cloud logging query generation
hamzabellouch/agent-skills/Google Cloud and GKE/cloud-logging-query-generation Skill
8★ repoGenerates Logging Query Language (LQL) queries for Google Cloud Logging from natural language. Use this skill when you need to query log data or when you are debugging issues. You can filter log data by Google Cloud service. Don't use this skill to query other databases, such as SQL or Spanner.
hamzabellouch/agent-skills/Google Cloud and GKE/gcloud Skill
8★ repoInteracts with Google Cloud services using the gcloud CLI safely and efficiently. Covers command validation, data reduction, safety guardrails with a denylist, and workflows for discovery and investigation. You MUST read this skill before invoking any gcloud command. Use when managing cloud resources, querying configurations, or troubleshooting issues via gcloud. Don't use when writing or debugging Google Cloud client library code or raw REST/gRPC API interactions.
hamzabellouch/agent-skills/Google Workspace Automation/gws-gws-gmail-triage Skill
8★ repoGmail: Show unread inbox summary (sender, subject, date).
The same file is in 4 other repositories
hamzabellouch/agent-skills/Software Engineering and Workflows/debugging-and-error-recovery Skill
8★ repoGuides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
The same file is in 2 other repositories
Workflow superpowers systematic debugging
hamzabellouch/agent-skills/Software Engineering and Workflows/workflow-superpowers-systematic-debugging Skill
8★ repoUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
The same file is in 8 other repositories
acquia/acquia-skills/skills/acli/troubleshooting Skill
8★ repoUse when acli commands fail, return unexpected errors, authentication breaks, or the CLI behaves unexpectedly.
The same file is in 1 other repository
ninthwave-io/ninthwave/skills/friction-triage Skill
8★ repoInteractively walk through every friction log in `.ninthwave/friction/` one at a time. For each log: read it, assess severity and possible duplicates, ask the human what to do (fix now / create work item / update doc / drop / merge / skip), execute the decision, and delete the log. This is the canonical way to clear the friction inbox: a synchronous, human-in-the-loop session. Use when asked to "triage friction", "review friction logs", "clear the friction inbox", or "walk through friction".
jscraik/Agent-Skills/Infrastructure/references/deferred-skill-context/agent-ops-triage Skill
8★ repoReview and triage file-based `todos/` findings into ready, skipped, or revised states before execution. Use this skill when the repo already uses the file-based todo workflow and the user wants approval-style triage, not tracker triage or todo execution.
jscraik/Agent-Skills/Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/he-fix-bugs Skill
8★ repoRestore broken behavior by reproducing failures, identifying root cause, and delivering verified fixes. Use when the user needs regression debugging, incident triage, or bug repair from tracker or direct reports.
jscraik/Agent-Skills/Skills/agent-ops/code-fixes-triage Skill
8★ repoTurn Slack #code-fixes, CodeRabbit, Codex Review, CI, and check-status noise into a repo-and-PR action queue. Use when Jamie asks for a daily code-fixes digest, recent review-noise triage, or what needs fixing across active engineering repos.
jscraik/Agent-Skills/Skills/agent-ops/triage Skill
8★ repoReview file-based todo findings into ready, skipped, customized, or blocked states. Use this skill when pending todo files need approval.
PIXARTSeu/Synapse/.agents/skills/debugging-wizard Skill
no license8★ repoParses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.
The same file is in 2 other repositories
PIXARTSeu/Synapse/.agents/skills/mcp-developer Skill
no license8★ repoUse when building, debugging, or extending MCP servers or clients that connect AI systems with external tools and data sources. Invoke to implement tool handlers, configure resource providers, set up stdio/HTTP/SSE transport layers, validate schemas with Zod or Pydantic, debug protocol compliance issues, or scaffold complete MCP server/client projects using TypeScript or Python SDKs.
The same file is in 1 other repository
PIXARTSeu/Synapse/.agents/skills/monitoring-expert Skill
no license8★ repoConfigures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules, and instruments distributed tracing. Implements Prometheus/Grafana stacks, conducts load testing, performs application profiling, and plans infrastructure capacity. Use when setting up application monitoring, adding observability to services, debugging production issues with logs/metrics/traces, running load tests with k6 or Artillery, profiling CPU/memory bottlenecks, or forecasting capacity needs.
The same file is in 1 other repository
PIXARTSeu/Synapse/skills/systematic-debugging Skill
no license8★ repoUse when encountering any bug, test failure, unexpected behavior, or error. Triggers on: "it's broken", "this doesn't work", "I'm getting an error", "fix this bug", any unexpected behavior. Requires finding root cause before attempting fixes. Symptom fixes are failure.
PIXARTSeu/Synapse/packages/codegraph/data/lifecycle-skills/debugging-wizard Skill
no license8★ repoParses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.
The same file is in 2 other repositories
PIXARTSeu/Synapse/packages/codegraph/data/lifecycle-skills/mcp-developer Skill
no license8★ repoUse when building, debugging, or extending MCP servers or clients that connect AI systems with external tools and data sources. Invoke to implement tool handlers, configure resource providers, set up stdio/HTTP/SSE transport layers, validate schemas with Zod or Pydantic, debug protocol compliance issues, or scaffold complete MCP server/client projects using TypeScript or Python SDKs.
The same file is in 1 other repository
PIXARTSeu/Synapse/packages/codegraph/data/lifecycle-skills/monitoring-expert Skill
no license8★ repoConfigures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules, and instruments distributed tracing. Implements Prometheus/Grafana stacks, conducts load testing, performs application profiling, and plans infrastructure capacity. Use when setting up application monitoring, adding observability to services, debugging production issues with logs/metrics/traces, running load tests with k6 or Artillery, profiling CPU/memory bottlenecks, or forecasting capacity needs.
The same file is in 1 other repository
PIXARTSeu/Synapse/packages/codegraph/data/lifecycle-skills/systematic-debugging Skill
no license8★ repoUse when encountering any bug, test failure, unexpected behavior, or error. Triggers on: "it's broken", "this doesn't work", "I'm getting an error", "fix this bug", any unexpected behavior. Requires finding root cause before attempting fixes. Symptom fixes are failure.
PIXARTSeu/Synapse/packages/codegraph/data/skill/docker Skill
no license8★ repoDocker MCP - gestione container Coolify, debug log, ispezione deployment, monitor risorse. Use when inspecting containers, debugging deployments, reading logs, or monitoring resource usage via Docker MCP.
PIXARTSeu/Synapse/packages/codegraph/data/skill/mongodb Skill
no license8★ repoMongoDB MCP - query dirette a Payload CMS collections, debug dati, analisi tenant, aggregazioni. Use when querying MongoDB directly, debugging Payload CMS data, running aggregations, or analyzing tenant collections.
PIXARTSeu/Synapse/packages/codegraph/data/skill/monitoring-nextjs Skill
no license8★ repoMonitoring and observability for Next.js — Sentry error tracking, structured logging with Pino, OpenTelemetry tracing, health checks, uptime monitoring, alerting. Use when adding error tracking, logging, performance monitoring, or alerting to a Next.js project.
PIXARTSeu/Synapse/packages/codegraph/data/skill/systematic-debugging Skill
no license8★ repoUse when encountering any bug, test failure, unexpected behavior, or error. Triggers on: "it's broken", "this doesn't work", "I'm getting an error", "fix this bug", any unexpected behavior. Requires finding root cause before attempting fixes. Symptom fixes are failure.