Debugging

Find and fix bugs, error analysis

Showing 553-576 of 4752 skills
mlflow

instrumenting-with-mlflow-tracing

by mlflow

Instruments Python and TypeScript code with MLflow Tracing for observability. Triggers on questions about adding tracing, instrumenting agents/LLM apps, getting started with MLflow tracing, or tracing specific frameworks (LangGraph, LangChain, OpenAI, DSPy, CrewAI, AutoGen). Examples - "How do I add tracing?", "How to instrument my agent?", "How to trace my LangChain app?", "Getting started with MLflow tracing", "Trace my TypeScript app"

Debugging 61 5mo ago
secondsky

sapui5-linter

by secondsky

Use this skill when working with the UI5 Linter (@ui5/linter) for static code analysis of SAPUI5/OpenUI5 applications and libraries. This skill should be used when: (1) Setting up UI5 Linter in a project for the first time, (2) Configuring linting rules and ignore patterns for UI5 codebases, (3) Running the linter to detect deprecated APIs, global variable usage, CSP violations, or manifest issues, (4) Using autofix to automatically correct deprecated API usage, global references, event handlers, and manifest properties, (5) Troubleshooting linting errors or warnings in UI5 code, (6) Integrating UI5 Linter into CI/CD pipelines or pre-commit hooks, (7) Preparing UI5 projects for migration to UI5 2.x by identifying compatibility issues, (8) Understanding and resolving specific linting rules like no-deprecated-api, no-globals, async-component-flags, or manifest validation rules. The skill covers all 19 linting rules, comprehensive autofix capabilities and limitations, CLI options, configuration patterns, performance optimization, and integration with development workflows. Keywords: SAPUI5, OpenUI5, UI5 Linter, @ui5/linter, static analysis, deprecated APIs, global variables, CSP, manifest.json, ui5.yaml, ESLint, pre-commit hooks, GitHub Actions, CI/CD, Node.js, TypeScript, XML, JSON, HTML, YAML, OData v2/v4, async, event handlers, jQuery, autofix, performance optimization, 19 linting rules, no-deprecated-api, no-globals, no-async-component-flags, manifest-v2, UI5 2.x migration

Processing 387 5mo ago
JetBrains

git-workflow

by JetBrains

IdeaVim git workflow conventions covering commits, branches, PRs, and CI. Use when creating commits, managing branches, creating pull requests, reviewing git history, or any git-related activity in the IdeaVim project.

Debugging 10.2K 5mo ago
astronomer

debugging-dags

by astronomer

Comprehensive DAG failure diagnosis and root cause analysis. Use for complex debugging requests requiring deep investigation like "diagnose and fix the pipeline", "full root cause analysis", "why is this failing and how to prevent it". For simple debugging ("why did dag fail", "show logs"), the airflow entrypoint skill handles it directly. This skill provides structured investigation and prevention recommendations.

Automation 411 5mo ago
daymade

github-contributor

by daymade

Strategic guide for becoming an effective GitHub contributor. Covers opportunity discovery, project selection, high-quality PR creation, and reputation building. Use when looking to contribute to open-source projects, building GitHub presence, or learning contribution best practices.

Code Review 1.3K 6mo ago
daymade

debugging-network-issues

by daymade

Evidence-driven investigation for network, streaming, and protocol-layer bugs. Use when debugging connection resets (ECONNRESET, HTTP/2 RST_STREAM, INTERNAL_ERROR), SSE or long-polling stalls, fixed-time connection drops, CDN/proxy/CGNAT idle timeouts, or any incident where symptoms do not match the obvious cause. Applies falsification-first methodology — layered isolation experiments to pin down the responsible network layer, env-gated runtime instrumentation for non-invasive observation, and counter-review agent teams to challenge single-cause assumptions. Strongly trigger on "socket closed unexpectedly", "stream interrupted", "ECONNRESET", "HTTP/2 INTERNAL_ERROR", "fails after N seconds", "works sometimes but not always", "upstream silent for X seconds", or any scenario where the investigator might jump to conclusions before evidence. Generalizes to any multi-layer system investigation where assumption-first thinking is the failure mode.

Debugging 1.3K 2mo ago
qwibitai

get-qodo-rules

by qwibitai

"Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards. Use before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning."

Processing 30.3K 4mo ago
redpanda-data

security-scan

by redpanda-data

Resolve npm dependency vulnerabilities detected by security scans.

Code Review 4.3K 6mo ago
windmill-labs

commit

by windmill-labs

Create a git commit with conventional commit format. MUST use anytime you want to commit changes.

Debugging 17.2K 5mo ago
dmmulroy

better-result-adopt

by dmmulroy

Migrate codebase from try/catch or Promise-based error handling to better-result. Use when adopting Result types, converting thrown exceptions to typed errors, or refactoring existing error handling to railway-oriented programming.

Code Gen 1.6K 5mo ago
qwibitai

qodo-pr-resolver

by qwibitai

Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)

Code Review 30.3K 4mo ago
databricks-solutions

databricks-mlflow-evaluation

by databricks-solutions

"MLflow 3 GenAI agent evaluation. Use when writing mlflow.genai.evaluate() code, creating @scorer functions, using built-in scorers (Guidelines, Correctness, Safety, RetrievalGroundedness), building eval datasets from traces, setting up trace ingestion and production monitoring, aligning judges with MemAlign from domain expert feedback, or running optimize_prompts() with GEPA for automated prompt improvement."

Agents 1.8K 5mo ago
cockroachdb

table-driven-test

by cockroachdb

Guidelines for creating clean, well-structured table-driven tests in Go following CockroachDB conventions.

Processing 32.3K 5mo ago
cockroachdb

commit-helper

by cockroachdb

Help create git commits and PRs with properly formatted messages and release notes following CockroachDB conventions. Use when committing changes or creating pull requests.

Code Review 32.3K 5mo ago
dbt-labs

troubleshooting-dbt-job-errors

by dbt-labs

Use when a dbt Cloud/platform job fails and you need to diagnose the root cause, especially when error messages are unclear or when intermittent failures occur. Do not use for local dbt development errors.

Processing 637 5mo ago
aiskillstore

python-best-practices

by aiskillstore

Provides Python patterns for type-first development with dataclasses, discriminated unions, NewType, and Protocol. Must use when reading or writing Python files.

Processing 395 6mo ago
cockroachdb

integration-test

by cockroachdb

Guidelines for writing integration tests with CockroachDB test servers, including when to use them and how to use sqlutils.

Database 32.3K 5mo ago
vudovn

brainstorming

by vudovn

Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.

Code Gen 7.8K 6mo ago
openshift

Code Formatting

by openshift

"MANDATORY: When writing Go tests, you MUST use 'When...it should...' format for ALL test names. When writing any Go code, you MUST remind user to run 'make lint-fix' and 'make verify'. These are non-negotiable HyperShift requirements."

Code Gen 536 9mo ago
proffesor-for-testing

performance-testing

by proffesor-for-testing

"Test application performance, scalability, and resilience. Use when planning load testing, stress testing, or optimizing system performance."

Debugging 420 5mo ago
proffesor-for-testing

n8n-integration-testing-patterns

by proffesor-for-testing

"API contract testing, authentication flows, rate limit handling, and error scenario coverage for n8n integrations with external services. Use when testing n8n node integrations."

API Dev 420 6mo ago
TheOrcDev

js-early-exit

by TheOrcDev

Use early returns to avoid unnecessary computation in loops and functions. Apply when processing arrays, validating input, or checking multiple conditions where the result can be determined before all iterations complete.

Debugging 2K 6mo ago
freekmurze

fix-github-issue

by freekmurze

Fix GitHub issues using gh CLI. Use when asked to fix, resolve, or address a GitHub issue. Creates fixes on separate branches, runs tests locally, and creates PRs when tests pass. Requires gh CLI authenticated and repo cloned locally.

Code Review 988 6mo ago
tuist

migrating-to-tuist-generated-projects

by tuist

Migrates existing Xcode projects to Tuist generated workspaces with build and run validation, external dependency mapping, and migration checklists. Use when adopting Tuist for an existing app or converting a hand-edited Xcode project to generated projects.

Code Gen 5.8K 5mo ago