Debugging
Find and fix bugs, error analysis
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.
receiving-code-review
by oyi77
Use when getting code feedback, before implementing suggestions.
moltbook-interact
by oyi77
Automate interactions on Moltbook - post content, engage with threads, and manage account
model-router
by oyi77
Intelligent model routing via subagents - automatically spawn the right model for each task complexity
insecure-defaults
by runkids
"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."
dwarf-expert
by runkids
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.
address-sanitizer
by runkids
AddressSanitizer detects memory errors during fuzzing. Use when fuzzing C/C++ code to find buffer overflows and use-after-free bugs.
fp-check
by runkids
"Systematically verifies suspected security bugs to eliminate false positives. Produces TRUE POSITIVE or FALSE POSITIVE verdicts with documented evidence for each bug."
java-best-practices
by Leavesfly
Java 编码最佳实践与设计模式
nix
by i9wa4
Nix commands and package management guide. Use when: - Running nix build, nix run - Adding custom packages - Using nurl for hash acquisition
git
by i9wa4
Git operations guide. Provides how-to for common git tasks. Use when: - Writing commit messages (Conventional Commits format) - Understanding git workflows
robius-matrix-integration
by ZhangHanDong
CRITICAL: Use for Matrix SDK integration with Makepad. Triggers on: Matrix SDK, sliding sync, MatrixRequest, timeline, matrix-sdk, matrix client, robrix, matrix room, Matrix 集成, 聊天客户端
makepad-router
by ZhangHanDong
"CRITICAL: Use for ALL Makepad/Robius questions including widgets, layout, events, and shaders.
sentry-ios-swift-setup
by getsentry
Setup Sentry in iOS/Swift apps. Use when asked to add Sentry to iOS, install sentry-cocoa SDK, or configure error monitoring, tracing, session replay, logging, or profiling for iOS applications using Swift and SwiftUI.
sentry-setup-logging
by getsentry
Setup Sentry Logging in any project. Use this when asked to add Sentry logs, enable structured logging, setup console log capture, or integrate logging with Sentry. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and other frameworks.
sentry-setup-tracing
by getsentry
Setup Sentry Tracing (Performance Monitoring) in any project. Use this when asked to add performance monitoring, enable tracing, track transactions/spans, or instrument application performance. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and Node.js.
fix-ci
by ryoppippi
Diagnoses and fixes CI failures with the gh CLI. Use when GitHub Actions checks are red and the failing logs need to be fetched, analysed, and resolved.
react-server-components
by ryoppippi
Reviews React Server/Client Component boundaries against Next.js and React docs. Use when auditing 'use client' placement or splitting components for proper RSC behaviour.
explore-plan
by AlexanderMattTurner
Drives the Explore -> Plan -> Critique -> Review -> Verify discipline for a written plan. Activate on entry to plan mode, before writing the plan — including the plan-mode requests "plan this", "scope this out", "figure out how to do X", "explore the codebase first" — in auto mode at the start of any non-trivial task, where no plan gate fires — and in any other mode when the task obviously needs a plan (several files, an unfamiliar subsystem, more than one PR), invoked informally without entering plan mode. A trivial edit (typo, single-line change) activates nothing, in any mode. Enforces a self-critiqued written plan, convergent setup work started in the background while design questions settle, and real verification instead of trusting a success claim.
fact-checking
by axiomantic
"Verify technical claims in code, docs, and comments via evidence-backed verdicts before merge."
debugging
by axiomantic
"Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work', 'X is broken', 'something's wrong', 'getting an error', 'exception in', 'stopped working', 'regression', 'crash', 'hang', 'flaky test', 'intermittent failure', or when user pastes a stack trace/error output. NOT for: test quality issues (use fixing-tests), adding new behavior (use implementing-features)."
async-await-patterns
by axiomantic
"Use when writing JavaScript or TypeScript code with asynchronous operations, fixing promise-related bugs, or converting callback/promise patterns to async/await. Triggers: 'promise chain', 'unhandled rejection', 'race condition in JS', 'callback hell', 'Promise.all', 'sequential vs parallel async', 'missing await'. Enforces async/await discipline over raw promises."
requesting-code-review
by axiomantic
"Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. Orchestrates multi-phase review (planning, context assembly, dispatch, triage, fix, gate). Dispatches code-review internally. NOT the same as finishing-a-development-branch (which handles merge/PR decisions after review passes)."
brainstorming
by axiomantic
"Use when exploring design approaches, generating ideas, or making architectural decisions. Triggers: 'explore options', 'what are the tradeoffs', 'how should I approach', 'let's think through', 'sketch out an approach', 'I need ideas for', 'how would you structure', 'what are my options'. Also used in SYNTHESIS mode when implementing-features provides discovery context for autonomous design."