القائمة
Spawn agent to trace code flow via query tools — answer only, no context cost
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill traceيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Audit all lint-ignore suppressions for appropriateness and overuse
Pre-flight checklist — run high-signal review skills before a release
Discover functions that block the main thread, then micro-audit each for internal optimization opportunities
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | trace |
| description | Spawn agent to trace code flow via query tools — answer only, no context cost |
| user-invocable | true |
| disable-model-invocation | false |
| context | fork |
| agent | Explore |
| argument-hint | <question about code flow> |
Trace the following code flow through the Alt-Tabby codebase: "$ARGUMENTS"
Run via powershell -File tools/<name>. These are the primary research tools — always prefer them over reading files directly.
query_callchain.ps1 <funcName> [-Depth N] [-Reverse]
Forward: shows what <funcName> calls, to N levels deep (default 2).
Reverse: shows what calls <funcName>, to N levels up.
Example: powershell -File tools/query_callchain.ps1 GUI_Repaint -Depth 3
query_function.ps1 <funcName>
Extracts full function body with line numbers. Use when you need to understand WHAT a function does, not just what it calls.
Example: powershell -File tools/query_function.ps1 GUI_TransitionTo
query_global_ownership.ps1 <globalName>
Shows who declares, writes (with mutation count), and reads a global.
Example: powershell -File tools/query_global_ownership.ps1 gGUI_State
query_mutations.ps1 <globalName> [-Brief]
Shows every function that mutates a global, with guards (Critical sections, if-conditions) and literal values assigned. More detailed than ownership.
Example: powershell -File tools/query_mutations.ps1 gGUI_State
query_impact.ps1 <funcName> [-Deep]
Shows callers, globals written, downstream readers of those globals.
-Deep adds transitive callers (callers of callers).
Example: powershell -File tools/query_impact.ps1 GUI_Repaint -Deep
query_interface.ps1 <filename>
Public functions + globals for a file (like help(module)). Accepts filename with or without .ahk extension.
Example: powershell -File tools/query_interface.ps1 gui_paint
query_includes.ps1 [filename]
No args: full include tree from entry points.
With filename: who includes this file, what it includes, transitive entry points.
Example: powershell -File tools/query_includes.ps1 gui_state.ahk
query_function_visibility.ps1 <funcName>
Where defined, public/private, all callers across all files.
Example: powershell -File tools/query_function_visibility.ps1 _GUI_FreezeDisplayList
query_config.ps1 [keyword | -Section <name> | -Usage <propertyName>]
No args: section/group index. Keyword: fuzzy search. -Usage: which files read cfg.X.
Example: powershell -File tools/query_config.ps1 -Usage ThemeMode
query_ipc.ps1 [message]
No args: list all IPC_MSG_* constants. With message: who sends/handles it.
Example: powershell -File tools/query_ipc.ps1 snapshot
query_state.ps1 [state] [event]
No args: index of all states/events. With args: specific dispatch branch.
Hardcoded to GUI_OnInterceptorEvent in gui_state.ahk.
Example: powershell -File tools/query_state.ps1 ACTIVE TAB_STEP
query_timers.ps1 [keyword]
No args: full SetTimer inventory. With keyword: fuzzy filter.
Example: powershell -File tools/query_timers.ps1 heartbeat
query_messages.ps1 [query]
No args: list all WM_ handlers. With query: hex, WM_ name, or handler function.
Example: powershell -File tools/query_messages.ps1 WM_CTLCOLORSTATIC
query_callchain.ps1 as the primary tracing toolquery_function.ps1 ONLY when call chain output doesn't explain what a step doesquery_global_ownership.ps1 or query_mutations.ps1 when the question involves data flow through globalsquery_impact.ps1 when the question is about what a change would affectquery_interface.ps1 to understand a module's API surface before diving into specificsReturn ONLY a synthesized answer in this exact format:
One sentence: what the flow does end-to-end.
Maximum 30 lines total. No raw tool output. No reasoning about your research process.