Results for “formula-debugging”
55 skillsspreadsheet-formula-helper
Write and debug spreadsheet formulas (Excel/Google Sheets), pivot tables, and array formulas; translate between dialects; use when users need working formulas with examples and edge-case checks.
66.9k
bambi-python
Use for writing, reviewing, debugging, testing, or diagnosing Bayesian regression and hierarchical models built with Bambi formulas, Model, Family/Likelihood/Link, Prior, fit, prior predictive, and predict. Trigger on common versus group-specific terms, categorical coding, family/link choice, automatic prior scaling, missing rows, PyMC backend settings, and InferenceData predictions. Do not use for hand-built PyMC graphs, NumPyro programs, ArviZ-only analysis of existing draws, frequentist statsmodels formulas, or generic pandas work.
0 · bundle
pyfixest-reference
Dense, machine-readable API reference for PyFixest — high-dimensional fixed-effects OLS/WLS/IV and Poisson (feols, fepois, feglm), clustered/robust standard errors, R-style formula syntax, and post-estimation. Use when writing or debugging Python fixed-effects regressions with the pyfixest package.
1k · bundle
More results
excel-formula-troubleshooter
Excel/Sheets Formula Troubleshooter
2
algebra-based-debugging
Algebra Based Debugging Skill
1 · bundle
algebra-debugging-expert
Algebra Debugging Expert Skill
1 · bundle
debugging
Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".
0
systematic-debugging
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
3
debugger
Provides a structured debugging workflow for analyzing errors, test failures, and unexpected behavior, including root cause analysis and fix recommendations.
42.4k
advanced-logic-debugging
Advanced Logic Debugging Skill
1 · bundle
debugging-wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs.
10.4k · bundle
debugging
Systematically diagnose and fix software bugs by analyzing error messages, stack traces, logs, and runtime behavior across multiple languages. Use when the user requests debugging or provides relevant inputs for this workflow.
159
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
1
debugger
Provides a structured debugging workflow for diagnosing errors, test failures, and unexpected behavior, including root cause analysis and verification steps.
5
debugging
Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".
0 · bundle
debugging
Debug application issues with techniques for Python, JavaScript, performance profiling, production incidents, and network problems.
1
debug-and-fix
Fix broken or failing functionality through structured reproduction, root-cause analysis, minimal fix, and verification. Load when the user asks to fix a bug, debug an error, resolve an issue, or work on a Linear ticket. Also triggers on "this is broken", "fix this bug", "why is this failing", "debug this", "resolve this error", "what went wrong", or any request to diagnose and fix a problem.
3 · bundle
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
1
debugger
Provides a structured debugging workflow for diagnosing errors, test failures, and unexpected behavior, including root cause analysis and fix verification.
3
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
0 · bundle
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
6
debug
Investigate a problem, log it to the debug changelog, cross-check past issues, and suggest a non-duplicate fix.
1 · bundle
systematic-debugging
Find root causes of bugs, test failures, or unexpected behavior before proposing any fixes.
247k · bundle
systematic-debugging
Enforces a disciplined, evidence-based debugging protocol. Use when the user reports a bug, an unexpected behavior, a broken test, or asks "why is X not working?". Prevents premature fixes and treats symptoms. Blocks code changes until a root cause is confirmed.
3 · bundle
debugging-patterns
Pattern-Based Diagnosis
1.7k · bundle
eng-debug
Diagnose and fix a bug through a disciplined reproduce, isolate, diagnose, fix, verify loop driven by evidence and one hypothesis at a time — not guesswork.
0
debugging-methodology
Debugging is the scientific method under time pressure.
2
systematic-debugging
Systematic Debugging
0 · bundle
systematic-debugging
Diagnose failures from runtime evidence before editing code.
4
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
23
debugging-strategies
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
23
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
2
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
23
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
1
debugger
Provides a structured debugging workflow for errors, test failures, and unexpected behavior, including root cause analysis and verification steps.
0
debugger
You are the debugger. You follow the scientific method: observe, hypothesize, test, conclude. You never guess-and-patch.
3