Results for “exception-tracking”

Debug agent execution by querying trace and metric tables, analyzing tool calls, durations, errors, and performance trends.

Agent skill for issue-tracker - invoke with $agent-issue-tracker

Progress Tracking

Investigates slow responses, tool failures, and guardrail rejections by querying agent trace logs and performance metrics.

Audit 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.

Track code changes with structured JSON records, an enforced state machine, and a session handoff format for AI continuity.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

Audit Trail

Systematically trace bugs backward through call stack to find original trigger

Provides patterns for robust error handling across TypeScript, Python, and Go, including typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

Handle errors as values using fp-ts Either and TaskEither, replacing try/catch with predictable, type-safe error handling patterns.

Audit Trail

Guides Apex exception handling design: catching expected failures, bulk DML semantics, boundary-specific error translation, and logging once at the right layer.

Implements error tracking and crash reporting in Flutter apps using Sentry and Firebase Crashlytics, including automatic error capture, enriched context, breadcrumbs, and CI/CD integration for source maps and debug symbols.

Follow a request end-to-end through the stack from route to database

Add EAS Observe to an Expo project for startup, navigation, and custom-event performance tracking, query metrics via the EAS CLI, and interpret results.

Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code

Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]

Logs the outcome of a skill execution to observations/<skill-name>/runs.md. Trigger on: "log this run", "skill worked", "skill failed", "this didn't work", "log the outcome", "record this", "note that", or after any skill completes with a clear success, partial, or failure outcome. Creates the observations file if it does not exist, then appends an entry with date, task description, skill used, outcome, what worked, what failed, and any error messages observed.

Append structured execution traces across operational, cognitive, and contextual surfaces with minimal overhead. Load when inspecting agent runs, logging tool calls and observations, enabling post-run debugging, or pairing with structured-planning step IDs. Also triggers on "trace this run", "log execution", "agent observability", "run log", or when fault-localize needs evidence. Default-on during multi-step plans. Traces live at .agent-loom/traces/ — git-ignored by default.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

Mirror issues and status across issue trackers with stable external-ID mapping to avoid duplicates. Load when syncing GitHub and Linear issues, mirroring ticket status, or keeping two trackers in sync. Also triggers on "issue sync", "sync issues", "mirror issues to", "keep Linear and GitHub in sync", or bidirectional issue tracker updates. Requires API access on both sides — stops if credentials missing.

Manages issues and dependencies through the Beads CLI, covering creation, updates, queries, and closure.

Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes

Project Tracking — Structured Active Project Files

User Request

Monitors a deployed URL for regressions after releases by checking HTTP status, console errors, network failures, performance metrics, content integrity, API health, static assets, and SSE streams.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans.

Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code

Implementation and taxonomy skill for analytics tracking — event naming, properties, tracking plans, GA4/GTM/Amplitude setup, and debugging. Use this for the "how do we actually wire this up" layer, not the "what should we measure and why" layer (that's `product-analytics` — use this skill alongside it, after the metrics/tracking-plan decisions are made). Use this — without waiting to be asked — whenever the user mentions "set up tracking," "GA4," "Google Analytics," "Amplitude," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "event taxonomy," "are my events firing," "why isn't this event showing up," "naming convention for events," or "instrument this feature." Produces a concrete tracking plan (event names, properties, triggers) plus implementation and debugging steps for the tools actually in use.

Gerencia issues no YouTrack Cloud via MCP oficial, incluindo busca, criação, comentários, tags, artigos e registro de trabalho, com fallback REST.

Incident Report (Blameless RCA)

从本地成本追踪数据库追踪并报告 Claude Code 的 Token 用量、花费与预算

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.