القائمة
Use when debugging a bug, tracing an error, narrowing a regression, or understanding why behavior changed. Keywords: debug, trace, regression, failing, broken, why does this fail.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Work in the build area — 66 symbols across 11 files (57% cohesion)
Work in the get area — 37 symbols across 12 files (27% cohesion)
Work in the glyph-canvas area — 41 symbols across 1 files (48% cohesion)
Work in the js area — 27 symbols across 1 files (36% cohesion)
Work in the src area — 31 symbols across 3 files (87% cohesion)
Work in the tests area — 38 symbols across 3 files (46% cohesion)
استنادا إلى تصنيف SOC المهني
| name | gortex-debug |
| description | Use when debugging a bug, tracing an error, narrowing a regression, or understanding why behavior changed. Keywords: debug, trace, regression, failing, broken, why does this fail. |
| argument-hint | symptom, error, or suspect area |
mcp_gortex_smart_context with the symptom, error text, or suspect subsystem.mcp_gortex_get_editing_context on the most relevant file from the first-pass result.mcp_gortex_get_processes when the bug looks flow-related.mcp_gortex_get_symbol_history to find churn-heavy symbols touched repeatedly in this session.mcp_gortex_get_dependents on a suspect symbol to see what else may be affected by a fix.activate_symbol_analysis_and_usage_tools for precise usages, callers, dependencies, and test targeting.activate_change_impact_analysis_tools when a proposed fix may have non-local consequences.activate_codebase_overview_and_health_tools if you suspect stale or incomplete indexing.mcp_gortex_smart_context with the message and subsystem keywords.mcp_gortex_get_symbol_history and then inspect dependents.mcp_gortex_get_processes and then pivot into file editing context.