- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
cluster-events
by scitix
Analyze cluster-wide Kubernetes events to identify issues and patterns. Aggregates Warning events, detects high-frequency patterns, and correlates related events.
query-tracing
by MaterializeInc
This skill should be used when the user wants to debug or trace where time is spent during query execution in Materialize. Trigger when the user mentions tracing queries, span analysis, query latency breakdown, Tempo traces, trace IDs, or wants to understand where time goes in CREATE TABLE, SELECT, INSERT, DROP, or any other SQL statement execution.
mz-profile
by MaterializeInc
This skill should be used when the user wants to "profile Materialize", "check memory usage", "analyze binary size", "debug performance", or mentions profiling, samply, heaptrack, flame graphs, memory checking, binary size analysis, slow queries, or high CPU/memory usage in the Materialize repository. Use this skill even if the user just says something is "slow" or "using too much memory" without explicitly mentioning profiling.
mz-commit
by MaterializeInc
This skill should be used when the user wants to "commit", "prepare a commit", "create a PR", "push", "open a pull request", or mentions committing, pre-commit checks, pull requests, or code review in the Materialize repository. Use this skill even if the user just says "ship it" or "ready to merge" without being specific.
Builder
by simota
å ç¢ãªãã¸ãã¹ãã¸ãã¯ã»APIçµ±åã»ãã¼ã¿ã¢ãã«ãåå®å ¨ãã¤ãããã¯ã·ã§ã³ã¬ãã£ã«æ§ç¯ããè¦å¾æ£ããã³ã¼ãã£ã³ã°è·äººããã¸ãã¹ãã¸ãã¯å®è£ ãAPIçµ±åãå¿ è¦ãªæã«ä½¿ç¨ã
1k-error-handling
by OneKeyHQ
Error handling patterns — try/catch, async errors, error boundaries, useAsyncCall, and toast messages.
1k-patching-native-modules
by OneKeyHQ
Patches native modules (expo-image, react-native, etc.) to fix native crashes or bugs.
devmoji
by lukevella
Devmoji commit message emoji conventions. Use when writing git commit messages, formatting commit descriptions, or choosing the right emoji prefix for a commit. Triggers on "commit message", "git commit", "commit emoji", "devmoji".
uloop-compile
by hatayama
"Compile Unity project. Use when: verifying code compiles after edits, checking for compile errors, or when user asks to compile. Returns error/warning counts."
fix-bug
by tddworks
Guide for fixing bugs in ClaudeBar following Chicago School TDD and rich domain design. Use this skill when: (1) User reports a bug or unexpected behavior (2) Fixing a defect in existing functionality (3) User asks "fix this bug" or "this doesn't work correctly" (4) Correcting behavior that violates the user's mental model
markdown
by DaveSkender
Format and validate Markdown files following GitHub Flavored Markdown standards with automated linting and manual semantic review
pr
by Automattic
INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment.
positron-intake-rotation
by posit-dev
This skill should be used when handling issue intake rotation duties for the Positron repository. It provides workflows for reviewing and organizing new issues, responding to discussions, handling support tickets, and searching for related content. Use this skill when on intake rotation duty, when helping someone with intake tasks, or when learning the intake rotation process.
positron-issue-creator
by posit-dev
This skill should be used when drafting GitHub issues for the Positron repository. It provides workflows for searching duplicates, selecting appropriate labels, gathering complete context through questioning, and writing terse, fluff-free issues that precisely describe what is needed or wrong. The skill prepares issues for manual submission by the user. Use this skill when the user asks to draft or prepare an issue for Positron.
fastq-analysis-pipeline
by Starlitnightly
Guide through omicverse's alignment module for SRA downloading, FASTQ quality control, STAR alignment, gene quantification, and single-cell kallisto/bustools pipelines covering both bulk and single-cell RNA-seq workflows.
jira-bulk-operations
by grandcamel
"Bulk operations for multiple issues at scale. TRIGGERS: 'bulk update', 'bulk close', 'bulk transition', 'bulk assign', 'transition N issues' (N >= 10), 'update all bugs', 'close 50 issues', 'mass transition', 'update multiple issues', quantities like '50 issues', '100 bugs', '20+ tickets'. Use for operations on 10+ issues. NOT FOR: single issue transitions (use jira-lifecycle), searching only without modifications (use jira-search), single issue field updates (use jira-issue)."
ci-cd-troubleshooting
by ruby-git
"Diagnoses and fixes CI/CD failures in GitHub Actions workflows. Use when CI is failing on a PR, builds are broken, or tests pass locally but fail in CI."
development-workflow
by ruby-git
"Follows a strict Test-Driven Development (TDD) workflow with four phases: triage, prepare, execute, and finalize. Use for bug fixes, feature implementation, refactoring, and maintenance tasks."
test-debugging
by ruby-git
"Debugs failing or flaky tests and improves test coverage. Use when tests fail consistently, exhibit intermittent behavior, or when adding missing test coverage."
go-best-practices
by NeverSight
Provides Go patterns for type-first development with custom types, interfaces, functional options, and error handling. Must use when reading or writing Go files.
dart-verify-sim
by dartsim
"DART Verify Sim: text-first and visual checks for 3D scenes and physics (metrics, scene dump, trajectories, headless render, image verdict/golden)"
dart-downstream-fix
by dartsim
"DART Downstream Fix: fix a DART bug reported through gz-physics or Gazebo"
dart-verify-sim
by dartsim
"DART Verify Sim: text-first and visual checks for 3D scenes and physics (metrics, scene dump, trajectories, headless render, image verdict/golden)"
receiving-code-review
by srbhr
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation