Debugging

Find and fix bugs, error analysis

Showing 1801-1824 of 5592 skills
bradsjm

home-assistant-automation-scripts

by bradsjm

Home Assistant automations, scripts, and blueprints. Use when the user requests automation/script syntax, triggers/conditions/actions, blueprint usage, run modes, or troubleshooting, and when mapping those needs to ha-mcp automation/script tools.

Automation 46 8mo ago
mycelium-io

troubleshooting

by mycelium-io

Diagnose and fix common Mycelium installation and runtime issues. Use when encountering errors with mycelium commands, backend connectivity, Docker containers, LLM configuration, or memory operations. Triggers on "not working", "error", "failed", "cannot connect", "troubleshoot", "debug", "fix".

CLI Tools 122 19d ago
existential-birds

go-middleware

by existential-birds

Idiomatic Go HTTP middleware patterns with context propagation, structured logging via slog, centralized error handling, and panic recovery. Use when writing middleware, adding request tracing, or implementing cross-cutting concerns.

API Dev 84 8mo ago
existential-birds

go-testing-code-review

by existential-birds

Reviews Go test code for proper table-driven tests, assertions, and coverage patterns. Use when reviewing *_test.go files.

API Dev 84 8mo ago
germanfndez

fivem-basics

by germanfndez

FiveM resource structure, fxmanifest, client/server scripting, events. Use when creating or editing FiveM resources or Lua scripts, or when the user asks how FiveM works.

Debugging 18 8mo ago
germanfndez

fivemanage

by germanfndez

Fivemanage SDK for FiveM — installation, screenshots (takeImage, takeServerImage, uploadImage), and centralized logs (Log, Info/Warn/Error). Use when integrating Fivemanage, capturing player screenshots, uploading images, or sending logs to the Fivemanage dashboard.

API Dev 18 8mo ago
germanfndez

lua-basics

by germanfndez

Effective Lua programming for FiveM - functions, tables, variables, conditionals, error handling. Use when writing or reviewing Lua code for FiveM resources.

Debugging 18 8mo ago
kylesnowschwartz

sc-think

by kylesnowschwartz

Socratic thinking partner for decisions, debugging mental models, and working through uncertainty. This skill SHOULD be used when the user says "I'm stuck", "should I", "can't decide", "not sure if", "is this the right approach", "what do you think about", "help me think through", "review my plan", "am I missing something", "what am I assuming", "let me think", "brainstorm", "help me figure out", "sanity check", "does this make sense", or expresses uncertainty about a decision, design, or direction. Activates dialectical reasoning to surface assumptions, challenge positions, and find the right question to ask.

Code Review 115 8mo ago
zhaono1

prd-implementation-precheck

by zhaono1

Implement PRDs/specs with a mandatory precheck review before coding. Use when a user asks to implement a PRD/feature spec/requirements doc or says "implement PRD/spec". Perform a preflight review, raise questions on scope/consistency/risks, then implement after confirmation.

Processing 84 9mo ago
kylesnowschwartz

hud-first

by kylesnowschwartz

This skill SHOULD be used when the user asks to "build an AI assistant", "create a chatbot", "make an agent that does X for me", "design a copilot feature", "automate this workflow with AI", or requests delegation-style AI features. Offers a reframe from copilot patterns (conversation, delegation) to HUD patterns (ambient awareness, perception augmentation).

Code Gen 115 8mo ago
zhaono1

debugger

by zhaono1

Advanced debugging specialist for diagnosing and resolving code issues. Use when user encounters bugs, errors, unexpected behavior, or mentions debugging.

Code Review 84 9mo ago
zhaono1

commit-helper

by zhaono1

Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits.

API Dev 84 9mo ago
zhaono1

session-logger

by zhaono1

Saves conversation history to session log files. Use when user says "保存对话", "保存对话信息", "记录会话", "save session", or "save conversation". Automatically creates timestamped session log in sessions/ directory.

Auth 84 9mo ago
tidyverse

types-check

by tidyverse

Validate function inputs in R using a standalone file of check_* functions. Use when writing exported R functions that need input validation, reviewing existing validation code, or when creating new input validation helpers.

Processing 5.1K 8mo ago
avivsinai

langfuse

by avivsinai

Debug AI traces, find exceptions, analyze sessions, and manage prompts via Langfuse MCP. Also handles MCP setup and configuration.

Code Gen 112 9mo ago
NTCoding

observability-first-debugging

by NTCoding

"Systematic debugging methodology that eliminates guessing and speculation. Add instrumentation to gather specific data that fully explains the problem. Evidence before hypothesis. Observation before solution. Triggers on: debugging, error investigation, 'why is this failing', unexpected behavior, test failures, non-zero exit codes, stack traces."

Processing 356 8mo ago
NTCoding

fix-it-never-work-around-it

by NTCoding

"Stops execution and fixes root cause when commands, builds, scripts, or tools fail unexpectedly. Triggers on workaround language: 'directly', 'instead', 'alternatively', 'skip', 'fall back', 'work around', 'isn't working', 'broken', 'manually'. Activates on any unexpected non-zero exit code or process failure."

CLI Tools 356 8mo ago
NTCoding

tdd-process

by NTCoding

"Strict test-driven development state machine with red-green-refactor cycles. Enforces test-first development, meaningful failures, minimum implementations, and full verification. Activates when user requests: 'use a TDD approach', 'start TDD', 'test-drive this'."

Code Review 356 8mo ago
NTCoding

writing-tests

by NTCoding

"Principles for writing effective, maintainable tests. Covers naming conventions, assertion best practices, and comprehensive edge case checklists. Based on BugMagnet by Gojko Adzic. Triggers on: writing any test, 'add tests', test review, test naming, assertion choices, edge case coverage, 'what should I test', test structure decisions."

Debugging 356 8mo ago
NTCoding

independent-research

by NTCoding

"Use when about to ask the user a factual question, propose a solution, diagnose an error, or choose between approaches. Triggers on: 'Do you have X installed?', 'What version?', 'Is X configured?', 'We should...', 'The fix is...', 'Options: 1...', 'Based on my understanding...', 'I believe X supports...'. Before deciding anything, spin up parallel subagents to WebSearch for current docs, community solutions, framework best practices, and GitHub issues. Your memory is stale — verify everything."

Code Review 356 8mo ago
OmniNode-ai

local-review

by OmniNode-ai

Local code review loop that iterates through review, fix, commit cycles without pushing

Code Review 4 7mo ago
transloadit

integrate-asset-delivery-with-transloadit-smartcdn-in-nextjs

by transloadit

Add Transloadit Smart CDN URL signing to a Next.js App Router project (server-side signing route + optional client demo page).

Code Gen 4 8mo ago
uze-sh

conformance-debug

by uze-sh

Fast, targeted debugging of the Harness Conformance Lab (conformance/) — use whenever a conformance check fails (locally or in CI), a check is recorded ADAPTED, a harness version drifted, a harness TUI check needs poking at directly, or you're about to guess at a fix instead of reproducing the real failure. Covers reading the failure's shape, checking the vendor's current docs/changelog/issues before touching code, the --sandbox and --experiment fast loops, proving the provider speaks the real wire shape with --discovery and mitmproxy, telling a vendor limitation from a Lab defect, and reading evidence/verdict.json.

CLI Tools 4 1mo ago
Lubu-Labs

langsmith-trace-analyzer

by Lubu-Labs

"Fetch, organize, and analyze LangSmith traces for debugging and evaluation. Use when you need to: query traces/runs by project, metadata, status, or time window; download traces to JSON; organize outcomes into passed/failed/error buckets; analyze token/message/tool-call patterns; compare passed vs failed behavior; or investigate benchmark and production failures."

Processing 107 8mo ago