Loading...
Loading...
Found 1,705 Skills
Diagnose, repair, and verify follow-up changes to an implementation already in progress.
Use when the user asks to implement agreed work, diagnose or fix a bug or performance regression, and verify the resulting outcome.
Проверить способ решения до того, как цена ошибки выросла. Использовать: перед нетривиальной фичей или дорогой развилкой; когда запрос описывает готовое решение вместо проблемы; перед редизайном, миграцией, унификацией или другой массовой правкой; перед второй правкой без новых фактов; после двух неудачных исправлений, повторного сообщения о том же симптоме или одной ложной победы. Не использовать как ритуал для мелких очевидных правок и продолжения уже согласованной работы.
Use this skill when you need to establish the cause of a failure, regression, anomaly, flaky behavior, or unexpected result. Focus on diagnosis, not implementing the fix.
Isolate root causes from defect descriptions, errors, logs, or reproductions through discriminating investigation and minimal feedback loops.
Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.
Use when a named runtime or compiler bug in a local repository needs independent reproduction.
Fix a bug — prove the cause, carry the smallest fix, leave it green. Use when the user says "fix" or "debug", reports an error, a stack trace, or wrong behaviour, or when another skill hands a regression back to the code. For a test that went red, use the fix-testing skill instead.
Fixes a bug by building a runnable reproduction and finding the root cause before any fix. Use for errors, crashes, failing tests or builds, flaky behavior, or repeated failed fixes.
Build a world the human drives until how a thing behaves is intuitive. Use when the user needs to hold how something behaves and reading has not made it intuitive.
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
Debug Rails issues systematically. Use when encountering ActiveRecord errors like RecordNotFound, routing issues, N+1 query problems detected by Bullet, asset pipeline issues, migration failures, gem conflicts, ActionController errors, CSRF token problems, or any Ruby on Rails application errors requiring diagnosis.