bitwisecook/tcl-lsp/irule-optimise

iRule Optimise

Apply the optimiser's rewrites to an iRule and explain each one.

Steps

1. Read ../_prompts/irules_system.md, then the iRule.
2. Call mcp__tcl-lsp__optimize with the contents as source (profile

defaults to the user's config.ini [optimiser] profile, else full; a named one wins; aggressive iterates to a fixpoint). On a tool error (e.g. a parse failure) report it and suggest fixes; on no findings report the code is already well-optimised.

1. Apply the returned optimised source with Edit.
2. For each optimisation, one or two sentences: why it preserves behaviour,

and what it gains on the hot path. A grouped item (constant propagation O100–O105 whose dead store O109 was then eliminated) is one transformation — explain it as one.

1. Re-validate with mcp__tcl-lsp__analyze on the rewritten source; revert

any optimisation that introduced an issue and say why.

1. Summarise what was applied.

Optimisation codes

Full table: docs/generated/optimisation_codes.md. Categories:

• Readability (O111, O114, O115, O117, O120, O128): idiomatic rewrites (incr, eq/ne, bracing)
• Constant folding/propagation (O100, O101, O102, O103, O105, O110, O113, O116, O118, O129): inline and simplify known values
• Pattern recognition (O104, O119, O130): fold string chains, pack consecutive sets
• Dead code (O107, O108, O109, O112, O124, O126): remove unreachable or unused code and stores
• Code motion (O106, O125, O127): hoist, sink, and inline assignments
• Recursion (O121, O122, O123): tail-call rewriting and accumulator hints

Profiles: off; readability (editor default: O111, O114, O115, O117, O120, O128); standard (readability + constant folding + pattern recognition); full (every pass, single pass; CLI/AI default); aggressive (every pass, to a fixpoint).

$ARGUMENTS