Debugging
Find and fix bugs, error analysis
dwarf-expert
by lv416e
Provides expertise for analyzing DWARF debug files and understanding the DWARF debug format/standard (v3-v5). Triggers when understanding DWARF information, interacting with DWARF files, answering DWARF-related questions, or working with code that parses DWARF data.
invariant-hunter-ts
by skyosev
Audit TypeScript types for weak invariants — unnecessary casts, loose optionality, defensive ?./?? masking missing guarantees, leaky discriminated unions, and runtime checks the type system should enforce. Use when: tightening domain models, reducing type assertions, increasing type coverage, reviewing discriminated unions, or establishing a type-safety baseline before refactoring.
invariant-hunter-go
by skyosev
Audit Go code for weak invariants — unchecked errors, nil pointer risks, ignored context cancellation, unsafe type assertions, zero-value traps, panic/recover misuse, and missing validation at construction boundaries. Use when: tightening domain models, reducing panic risks, increasing error handling discipline, or establishing a safety baseline before refactoring.
code-change-verification
by EYH0602
Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
intent-critique
by ArcBlock
Critical review of Intent design quality. Checks for over-engineering, YAGNI violations, premature abstraction, and simplification opportunities. Uses interactive discussion to refine design decisions.
systematic-debugging
by third774
Four-phase debugging framework with root cause tracing - understand the source before proposing fixes. Use when investigating bugs, errors, unexpected behavior, or failed tests.
defense-in-depth
by lv416e
"Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible 無効なデータが実行の深い部分で障害を引き起こす場合、複数のシステム層での検証が必要な際に使用 - データが通過するすべての層で検証し、バグを構造的に不可能にする"
mikrotik-routeros-rsc
by alexandre-machado
"Creation, editing, and review of RouterOS scripts (.rsc) with focus on idempotency, security, and best practices. Use when you need to generate, adjust, or import .rsc files for MikroTik: (1) create new configurations via script, (2) edit existing scripts with safe corrections, (3) review risks and execution policies, (4) validate with import dry-run and error handling."
adversarial-code-review
by third774
Review code through hostile perspectives to find bugs, security issues, and unintended consequences the author missed. Use when reviewing PRs, auditing codebases, or before critical deployments.
cfd-bioreactor
by dangeles
Use when user needs to simulate fluid flow through bioprocess cartridges, bioreactor geometries, or membrane devices using FEniCSx. Covers Navier-Stokes flow, O2 species transport with Michaelis-Menten kinetics, membrane permeation, mesh generation from CAD geometry, and interactive 3D visualization.
isentinel
by christopher-buss
Opinionated preferences for roblox-ts development. Use when setting up new roblox-ts projects or when coding style/tooling decisions arise.
test-hunter-ts
by skyosev
Audit TypeScript test code for quality gaps — missing coverage on critical paths, brittle tests coupled to implementation, over-mocking, assertion-free tests, missing edge cases, and duplicated test setup. Focuses on test effectiveness, not production code structure. Use when: reviewing TypeScript test suites for reliability, reducing false-positive test failures, improving coverage of critical business logic, or cleaning up test debt.
slop-hunter-go
by skyosev
Audit Go code for AI-generated noise — redundant comments, verbose documentation, style drift from project conventions and gofmt, trivially dead code, and unnecessary error wrapping. Surface-level hygiene pass; defaults to branch diff but supports any scope. Use when: reviewing AI-assisted Go code before merge, cleaning up generated code, enforcing project style on new contributions, or reducing review noise.
test-hunter-go
by skyosev
Audit Go test code for quality gaps — missing coverage on critical paths, brittle tests coupled to implementation, over-mocking, assertion-free tests, missing edge cases, table-driven test misuse, and race condition blindness. Focuses on test effectiveness. Use when: reviewing Go test suites for reliability, reducing false-positive test failures, improving coverage of critical business logic, or cleaning up test debt.
latex-autofix
by mseok
"LaTeX compilation with autonomous error resolution. Build artifacts go to out/, PDF is copied back to source directory. Parses logs, auto-fixes known errors (missing packages, font conflicts, citation issues, bad paths, stale cache), and runs citation audit on success."
go-easy
by marcfargas
Google APIs made easy — Gmail, Drive, Calendar, Tasks. Unified library and gateway CLIs (go-gmail, go-drive, go-calendar, go-tasks) for AI agents. Use when user needs to work with Gmail, Google Drive, Google Calendar, or Google Tasks. Replaces gmcli, gdcli, gccli.
address-review
by v1-io
Use when addressing PR review comments from Copilot, bots, or humans. Triggers on "fix review comments", "address Copilot feedback", "respond to PR comments".
systematic-debugging
by lv416e
"Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions バグ、テスト失敗、予期しない動作に遭遇した際、修正を提案する前に使用 - 4フェーズフレームワーク（根本原因調査、パターン分析、仮説検証、実装）により、解決策を試す前に理解を確保"
python-coder
by DmitriyYukhanov
Implements Python code following PEP 8, type hints, and project conventions. Use when implementing features designed by python-architect.
insecure-defaults
by lv416e
"Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing security, reviewing config management, or analyzing environment variable handling."
test-driven-development
by lv416e
"Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first 機能やバグ修正を実装する際、実装コードを書く前に使用 - まずテストを書き、失敗を確認し、最小限のコードで通す。最初に失敗を求めることで、テストが実際に動作を検証することを保証"
verification-before-completion
by third774
Run verification commands before claiming work is complete or fixed. Use before asserting any task is done, bug is fixed, tests pass, or feature works.
unity-coder
by DmitriyYukhanov
Use when implementing Unity C# code to follow proper coding guidelines, naming conventions, member ordering, and Unity-specific patterns
debugging-tauri-apps
by dchuk
Helps users debug Tauri v2 applications across VS Code, RustRover, IntelliJ, and Neovim. Covers console debugging, WebView DevTools, Rust backtrace, CrabNebula DevTools integration, and IDE-specific launch configurations.