Results for “exception-tracking”

Progress Tracking

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

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.

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

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]

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.

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

从本地成本追踪数据库追踪并报告 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".

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

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

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

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

Implement modern PHP error and exception handling patterns. Use when implementing exception hierarchies, error handlers, or custom exceptions in PHP.

Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.

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.

Design, review, and troubleshoot Salesforce Flow fault handling with error logging and bulk-safe automation paths.