Depuració
Detecció i correcció de problemes i anàlisi d’errors
claude-superpowers
mohitagw15856
"Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist."
gitnexus-debugging
abhigyanpatwari
"Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\""
gitnexus-exploring
abhigyanpatwari
"Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\""
condor-strategy
Senpi-ai
CONDOR v4.0.1 — One Amazing Trade per Day. Top 50 HL assets, pure trend continuation, apex confluence only. 3TF alignment hard gate + MACRO_TREND_GATE + SM consensus >=70%, MIN_SCORE 12, score-scaled sizing (50%/70%/80%), 10x leverage cap, 6-tier DSL ladder from Kodiak SOL empirical wins. v4.0.1 ships a race-window dedup cache that eliminates the ENGINE_FAILURE retry noise on already-held assets, plus a doubled DSL exit interval to throttle REDUCE_ONLY spam when runtime position-state lags HL.
jaguar-strategy
Senpi-ai
JAGUAR v4.0.0 — Striker (rank-jump detector), senpi_runtime_helpers migration. Plumbing-only flip from openclaw-CLI subprocess + mcporter subprocess + cron-driven self-executing scanner to in-process SenpiClient + long-lived producer_daemon + helpers-native push_signal. Thesis preserved verbatim from v3.7: violent FIRST_JUMP signals, rank-jump ≥ 10, MIN_SCORE 9, conviction-scaled leverage (10x apex / 7x conviction), 15m velocity hard gate, $3M day-notional liquidity floor, XYZ ban, one-amazing-trade-per-day discipline. Risk policy: max 3 entries/day when day is RED, unlimited when GREEN (cap losers, ride winners).
qa-test-planner
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
OneKeyHQ
Error handling patterns — try/catch, async errors, error boundaries, useAsyncCall, and toast messages.
changelog
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.
trace
Yeachan-Heo
Show agent flow trace timeline and summary
code-review
Yeachan-Heo
Run a comprehensive code review
doctor
Yeachan-Heo
Diagnose and fix oh-my-codex installation issues
learner
Yeachan-Heo
Extract a learned skill from the current conversation
analyze
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
Yeachan-Heo
Full autonomous execution from idea to working code
ultraqa
Yeachan-Heo
QA cycling workflow - test, verify, fix, repeat until goal met
build-fix
Yeachan-Heo
Fix build and TypeScript errors with minimal changes
ai-slop-cleaner
Yeachan-Heo
Run an anti-slop cleanup/refactor/deslop workflow
differential-audit
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
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
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
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
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.
gemini-scribe-help
allenhutchison
Answer questions about Gemini Scribe plugin features, settings, and usage, and diagnose plugin errors by reading the user's debug.log (when File Logging is enabled). Activate this skill whenever the user asks how to use the plugin or configure settings, OR reports that something went wrong with the plugin — bug, error, crash, broken behavior, "not working", "what just happened" — especially when they mention the debug log, log file, console output, or want help troubleshooting. Always activate this skill before searching the vault for plugin log files; debug.log lives in the plugin state folder which the standard read_file tool blocks.
diagnosing-bugs
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.