القائمة
Review error handling, logging, exception clarity, and debugging seams so failures stay visible and testable.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | dandy-code-error-observability |
| description | Review error handling, logging, exception clarity, and debugging seams so failures stay visible and testable. |
| argument-hint | [file, diff, log flow, or code snippet] |
Use this skill when code catches exceptions, suppresses failures, logs inconsistently, reports vague errors, or requires step debugging to understand behavior.
The output should preserve visibility into failures and make the code easier to test without an interactive debugger.
This skill may read and edit source and tests when asked to fix error handling. Do not change production logging infrastructure without explicit user approval.
Use configured artifact language for review notes and generated messages where appropriate. Keep exception class names and logger API names aligned with the project stack.
Review AI-assisted code changes for continuation bias, missing context, architectural asymmetry, security gaps, and code ownership.
Review method and object APIs for argument count, option shape, boolean flags, object parameters, and fluent configuration.
Identify small, reusable components that can be isolated from a large codebase without prematurely forcing microservices.
Simplify control flow with early returns, shallow nesting, explicit conditions, and readable branching.
Review whether code works with framework conventions instead of fighting them with unnecessary abstractions, mixed ecosystems, or upgrade-hostile choices.
Review and improve names for variables, methods, classes, files, routes, booleans, units, and paired operations.
