Debugging
Find and fix bugs, error analysis
qa-test-planner
by fugazi
Generate comprehensive test plans, manual test cases, automated Playwright tests, regression test suites, and bug reports for QA Automation engineers. Includes Playwright MCP integration for browser-based test execution and validation.
1k-error-handling
by OneKeyHQ
Error handling patterns — try/catch, async errors, error boundaries, useAsyncCall, and toast messages.
changelog
by kubb-labs
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
signal-over-noise
by JamieMason
Maximize useful information per word by removing filler, obvious explanations, and hedging language. Use when writing documentation, error messages, code comments, or any communication where clarity and conciseness matter.
front-loading
by JamieMason
Put the answer first, then context and details follow. Use when writing documentation, tutorials, error messages, or any communication where readers need to decide quickly if something is relevant to them.
add-feature
by JamieMason
Add new features to Syncpack including commands and validation logic. Use when implementing new CLI commands, adding InstanceState variants, or extending version group behaviour.
write-code
by JamieMason
Rust code style and conventions for Syncpack. Use when writing or modifying Rust code. Covers functional patterns, imports, naming, and quality standards.
trace
by Yeachan-Heo
Show agent flow trace timeline and summary
code-review
by Yeachan-Heo
Run a comprehensive code review
doctor
by Yeachan-Heo
Diagnose and fix oh-my-codex installation issues
learner
by Yeachan-Heo
Extract a learned skill from the current conversation
analyze
by Yeachan-Heo
"Run deep investigation of architecture, bugs, performance issues, or dependencies and return structured findings with file:line evidence. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs root cause analysis before making changes. Routes to architect agent or Codex MCP for thorough cross-file reasoning."
autopilot
by Yeachan-Heo
Full autonomous execution from idea to working code
ultraqa
by Yeachan-Heo
QA cycling workflow - test, verify, fix, repeat until goal met
build-fix
by Yeachan-Heo
Fix build and TypeScript errors with minimal changes
ai-slop-cleaner
by Yeachan-Heo
Run an anti-slop cleanup/refactor/deslop workflow
differential-audit
by pedrohcgs
Compare two implementations of the same thing — a port (R↔Python↔Stata), a reimplementation, a replication package, a refactor, or a new version against the old — so that agreement means something. Freeze inputs first, inventory every expected output, test the comparator itself, compare every channel (not just the headline number), and give each divergence a stable ID and a smallest witness. Use for cross-language parity, replication, upgrade/regression gates, or whenever "the numbers match" is about to license a claim.
diagnose
by pedrohcgs
Root-cause a failing or wrong empirical result with a disciplined reproduce → minimise → hypothesise → instrument → fix loop, instead of guessing-and-poking. Use when the user says "why is my regression wrong", "this number changed", "my script errors out", "the result won't reproduce", "debug this", "this estimate looks wrong", or "it worked yesterday". Tuned for research code (R/Stata/Python): type coercion, NA/merge blow-ups, factor levels, clustering/SE choices, weighting, collinearity/convergence, seeds, package-version drift. Use --no-fix to localize the root cause without editing shared or load-bearing files.
always-verify-gcp
by rominirani
A workflow skill for all Google Cloud resource management tasks (create, delete, modify). This skill ensures that the correct CLI tool (gcloud, bq, gsutil) is chosen and that its commands are verified against the latest official documentation before execution.
playwright-debug
by voicetreelab
This skill should be used when the user asks to "debug the electron app", "connect playwright to VoiceTree", "take screenshots of the running app", "interact with the live UI", "inspect the running application", or "test UI elements live". Provides step-by-step instructions for connecting Playwright MCP to a running Electron app for live debugging and automation.
apply-mantel-styles
by sammcj
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
diagnosing-bugs
by tt-a1i
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
rev-unicorn-debug
by P4nda0s
Debug and emulate specific code fragments or functions using the Unicorn engine. Activate when the user wants to emulate a function with Unicorn, trace binary execution without running the full program, decrypt or decode data by emulating the algorithm, or bypass environment dependencies (JNI, syscalls, libc) during emulation.
git-advanced-workflows
by HermeticOrmus
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.