菜单
Fix issues in an F5 iRule using LSP diagnostics. Runs an iterative analyse-fix-reanalyse loop until clean or stable. Use when fixing iRule errors, resolving iRule warnings, auto-fixing iRule lint issues, or cleaning up F5 iRule diagnostics.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | irule-fix |
| description | Fix issues in an F5 iRule using LSP diagnostics. Runs an iterative analyse-fix-reanalyse loop until clean or stable. Use when fixing iRule errors, resolving iRule warnings, auto-fixing iRule lint issues, or cleaning up F5 iRule diagnostics. |
| allowed-tools | Bash, Read, Edit |
Fix diagnostics in an iRule iteratively using LSP analysis.
ai/prompts/irules_system.mduv run --no-dev python ai/claude/tcl_ai.py diagnostics $FILE
uv run --no-dev python ai/claude/tcl_ai.py diagnostics $FILE
See docs/generated/diagnostic_codes.md for the full auto-generated table of all diagnostic codes.
$ARGUMENTS
Compare our compiler's bytecode output against tclsh reference disassembly (8.4, 8.5, 8.6, 9.0). Use when verifying bytecode correctness, investigating instruction sequence differences, or checking that our codegen matches C Tcl.
Debug the Tcl compiler pipeline (lexer → green tree → segmenter → IR → CFG → SSA → codegen) running from source — never a built pyz/zipapp. Wraps the tcl-explorer CLI and adds source-slice and raw-token views that make off-by-one range bugs obvious. Use when investigating a wrong diagnostic position, a stray-brace / unmatched-delimiter false positive, a mis-tokenised word, an IR statement whose range looks wrong, or any time you need to see what the compiler produces for a snippet of Tcl.
Download and extract Tcl source trees (8.4, 8.5, 8.6, 9.0) to tmp/ for test suites and bytecode reference. Idempotent — skips versions already present.
Manage differential-fuzzer findings: query fixed/unfixed status, list by category, verify findings against the current VM, mark findings as fixed/unfixed, and batch-update categories. Use when working on fuzz findings, checking what's fixed, or triaging new results.
Use when verifying Tcl LSP server behavior: semantic tokens, diagnostics, formatting, hover, completion, definition, references, code actions, optimizations, document symbols, diagram extraction, event/command registry lookups, or benchmarking server performance and collecting timing logs. Tests the server directly over JSON-RPC without VS Code.
Query reference test results captured from real tclsh (8.4–9.0). Look up individual tests, search groups, view suite summaries, and compare results across Tcl versions.