Debugging
Find and fix bugs, error analysis
connectrpc
by wcygan
ConnectRPC expert for Go servers and Node.js clients. Auto-loads when working with ConnectRPC, connect-go, connect-node, protobuf RPC, buf codegen, gRPC-compatible APIs, streaming RPCs, ConnectError, interceptors, service handlers, transport configuration, or REST-to-RPC proxy patterns. Covers the architecture where Node frontend servers proxy REST+JSON from the UI into ConnectRPC calls to Go backend services.
axum
by wcygan
Axum Rust web framework expert. Auto-loads when working with axum Router, handlers, extractors, FromRequest, IntoResponse, State, middleware, tower layers, tower-http, axum::serve, method routing, Json extractor, Path extractor, Query extractor, error handling, or Rust HTTP APIs. Keywords: axum, router, handler, extractor, middleware, tower, IntoResponse, FromRequest, State, Rust web, HTTP API
commit
by wcygan
Analyze staged changes and create a well-crafted conventional commit. Handles unstaged files, pre-commit hook failures, and multi-file changes. Use when ready to commit, or when you want help writing a good commit message. Keywords: commit, git commit, stage, conventional commit, commit message
idiomatic-rust
by wcygan
Analyze and generate idiomatic Rust code following official style guide, std library conventions, and API design guidelines. Auto-loads when writing, reviewing, or refactoring Rust code. Use when writing Rust, reviewing Rust code, checking Rust idioms, or generating Rust scaffolding. Keywords: rust, idiomatic, ownership, borrowing, lifetime, trait, error handling, pattern matching, clippy, rustfmt, cargo
debug-team
by wcygan
Debug complex issues using an agent team with competing hypotheses. Spawns 3-5 investigators that actively challenge each other's theories and converge on the root cause. Use for tough bugs where the root cause is unclear. Keywords: debug team, competing hypotheses, root cause, investigation, multi-agent debug, hard bug, mystery bug
expand-tests
by wcygan
Analyze existing test patterns and create comprehensive, idiomatic tests to expand coverage. Detects framework (Jest, Vitest, pytest, Go, Rust, JUnit), matches project conventions, and fills coverage gaps. Use when adding tests, improving coverage, expanding test suite, or writing tests for untested code. Keywords: test, tests, testing, coverage, unit test, integration test, expand tests, test coverage, write tests, add tests, test gaps
fix
by parcadei
Meta-skill workflow orchestrator for bug investigation and resolution. Routes to debug, implement, test, and commit based on scope.
explicit-identity
by parcadei
Explicit Identity Across Boundaries
base44-troubleshooter
by base44
Troubleshoot production issues using backend function logs. Use when investigating app errors, debugging function calls, or diagnosing production problems in Base44 apps.
debugging
by SimHacker
Systematic bug investigation with hypothesis tracking
code-generation
by romiluz13
"Internal skill. Use cc10x-router for all development tasks."
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 集成, 聊天客户端
robius-event-action
by ZhangHanDong
CRITICAL: Use for Robius event and action patterns. Triggers on: custom action, MatchEvent, post_action, cx.widget_action, handle_actions, DefaultNone, widget action, event handling, 事件处理, 自定义动作
makepad-router
by ZhangHanDong
"CRITICAL: Use for ALL Makepad/Robius questions including widgets, layout, events, and shaders.
makepad-reference
by ZhangHanDong
CRITICAL: Use for Makepad troubleshooting and reference. Triggers on: troubleshoot, error, debug, fix, problem, issue, no matching field, parse error, widget not found, UI not updating, code quality, refactor, responsive layout, adaptive, api docs, reference, documentation, 故障排除, 错误, 调试, 问题, 修复
code-smell-detector
by rysweet
Identifies anti-patterns specific to amplihack philosophy. Use when reviewing code for quality issues or refactoring. Detects: over-abstraction, complex inheritance, large functions (>50 lines), tight coupling, missing all exports. Provides specific fixes and explanations for each smell.
error-detective
by htlin222
Search logs and codebases for error patterns, stack traces, and anomalies. Use when debugging issues, analyzing logs, or investigating production errors.
sc-troubleshoot
by htlin222
Diagnose and resolve issues in code, builds, or system behavior. Use when debugging errors, investigating build failures, or resolving deployment issues.
c-lang
by htlin222
Write efficient C code with proper memory management and system calls. Use for C optimization, memory issues, or system programming.
sc-build
by htlin222
Build, compile, and package projects with error handling and optimization. Use when user needs to build, compile, or package a project.
debug
by htlin222
Debug errors, test failures, and unexpected behavior with log analysis and correlation. Use when encountering issues, error messages, analyzing logs, or investigating production errors.
erpnext-impl-whitelisted
by OpenAEC-Foundation
"Implementation workflows and decision trees for Frappe Whitelisted Methods (REST APIs). Use when determining HOW to implement API endpoints: public vs authenticated, permission patterns, error handling, response formats, client integration. Triggers: how do I create API, build REST endpoint, frappe.call pattern, API permission check, guest API, secure endpoint."
erpnext-errors-clientscripts
by OpenAEC-Foundation
"Error handling patterns for ERPNext/Frappe Client Scripts. Use when implementing try/catch, user feedback, server call error handling, validation errors, and debugging. Covers async error handling, graceful degradation, and user-friendly error messages. V14/V15/V16 compatible. Triggers: client script error, try catch, frappe.throw, error handling, async error, validation error."
erpnext-errors-serverscripts
by OpenAEC-Foundation
"Error handling patterns for ERPNext Server Scripts. Use when handling sandbox errors, frappe.throw usage, validation in server scripts, and debugging. V14/V15/V16 compatible. Triggers: server script error, frappe.throw, sandbox error, validation error, debugging server script."