Debugging
Find and fix bugs, error analysis
help-and-support
by financedistrict-platform
Get help, onboarding guidance, and report issues. Use when you or the user need help with the wallet, have questions about how things work, want a walkthrough, are getting started for the first time, or need to report a bug or problem. Covers "how do I use this?", "help me get started", "I'm new", "something is broken", "report a bug", "what version is this?".
java-code-review
by theepan
Review Java source code for bugs, security vulnerabilities, performance problems, concurrency issues, AI-generated code quality issues, dependency licensing risks, and best practice violations. Use when a user asks to review Java code, audit Java files, find bugs in Java, check Java code quality, detect AI slop, check library licenses, or perform a code review on .java files. Accepts code provided directly, as local file paths, as directory paths, or as unified diff output.
common-changelog
by octivi
Draft and normalize user-facing CHANGELOG.md entries in Common Changelog format from release notes, pull requests, and Conventional Commits (including git trailers like Category, Ref, and Co-authored-by). Use this skill whenever the user asks for changelog text, release notes, "what changed", version summaries, or Unreleased notes, even if they do not explicitly mention CHANGELOG.md.
bug
by MartinNevlaha
"Bug-fixing workflow coordinator (analyze→fix→review→complete). Orchestrates debugging and repair by delegating to specialized agents."
mixseek-debug
by drillan
MixSeek-Plusのデバッグ機能を有効化し、ログ出力を制御します。「デバッグモードを有効化」「verbose」「ログを出力」「ログレベル」「デバッグ設定」といった依頼で使用してください。
product-brainstorm
by elliottrjacobs
Guided requirements exploration through structured dialogue. Use when the user says "brainstorm", "explore this idea", "help me think through", or when requirements are fuzzy and need clarification before writing specs.
essay-review
by clyderankin
The tough New York Times editor—diagnose structural problems, weak arguments, and voice drift
konditional
by amichne
Use this skill when integrating Konditional into a codebase — whether you are a new user defining your first typed namespace or an enterprise team migrating from string-key flag systems. Covers namespace declaration, context modeling, evaluation, remote config loading, gradual rollout, shadow migration, and OpenFeature interoperability.
bug-hunter
by k1lgor
Use this when the user reports an error, a crash, a bug, or provides a stack trace.
four-shuttle-wcs
by vanessamomo082-tech
P&G Huangpu Four-Way Shuttle立体库WCS系统知识技能。 适用于：(1)四项穿梭车立体库的库存管理问题(2)处理出入库任务异常(3)理解与WES/AGV的接口对接逻辑(4)查询业务解析配置(5)了解闲时理货逻辑
systematic-debugging
by Krosebrook
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
enumeration-protocol-execution
by starwreckntx
Enforce a Divergent-Convergent Scan loop to overcome 'Prevalent Noun Bias' and statistical probability reflexes (System 1).
root-cause-tracing
by Krosebrook
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
seer-code-review
by codyde
Analyze, validate, and fix issues identified by sentry bot in GitHub Pull Request reviews. Use this when asked to review or address sentry bot comments on PRs. Can review specific PRs by number or automatically find recent PRs with sentry comments.
test-driven-development
by Krosebrook
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
test-fixing
by Krosebrook
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass. Activates on phrases like "fix the tests", "tests are failing", or "make the test suite green".
agent-memory
by WHQ25
Long-term memory for AI coding agents via agmem CLI. Persist cross-project knowledge — bug fixes, library quirks, design decisions, user preferences — across sessions. Use when: (1) fixing a non-trivial bug worth remembering, (2) discovering undocumented library/API behavior, (3) making architecture decisions, (4) user corrects your approach or states a preference, (5) starting a new task and want to check for prior knowledge, (6) encountering an error that might have been seen before.
task-status
by addozhang
Send short status descriptions in chat for long-running tasks. Use when you need to provide periodic updates during multi-step operations, confirm task completion, or notify of failures. Includes automated periodic monitoring that sends updates every 5 seconds, status message templates, and a helper function for consistent status reporting.
zodipus-troubleshooting
by bratsos
Debug and fix Zodipus errors. Use when validation fails, generation errors occur, types don't match, Query Engine behaves unexpectedly, or user encounters any zodipus-related error.
backend-development
by pluginagentmarketplace
Backend development - APIs, authentication, business logic
asynchronous
by pluginagentmarketplace
Master asynchronous JavaScript patterns including callbacks, promises, async/await, event loop mechanics, and real-world async patterns.
gs-bun-aws-lambda
by gilbertopsantosjr
Bun AWS Lambda handlers with Clean Architecture adapter pattern. Handlers resolve Use Cases from DI Container and map domain exceptions to HTTP responses. Covers deployment patterns and cold start optimization.
deep-debug
by fefogarcia
Multi-agent investigation for stubborn bugs. Use when: going in circles debugging, need to investigate browser/API interactions, complex bugs resisting normal debugging, or when symptoms don't match expectations. Launches parallel agents with different perspectives and uses Chrome tools for evidence gathering.
openharmony-error-detection
by mengfei0053
Use when developing OpenHarmony applications to detect and fix errors systematically through lint, unit tests, compilation, automated search, and documentation lookup