Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

irule-diff

Sterne56

Forks6

Aktualisiert11. April 2026 um 16:02

Compare two iRule versions and explain the semantic differences, security implications, performance changes, and breaking changes. Uses LSP context analysis on both files. Use when comparing iRule versions, diffing F5 iRules, analysing iRule change impact, or reviewing iRule modifications.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

bitwisecook

bitwisecook/tcl-lsp

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	irule-diff
description	Compare two iRule versions and explain the semantic differences, security implications, performance changes, and breaking changes. Uses LSP context analysis on both files. Use when comparing iRule versions, diffing F5 iRules, analysing iRule change impact, or reviewing iRule modifications.
allowed-tools	Bash, Read

iRule Diff

Compare two iRule versions and analyse the differences.

Steps

Read the domain knowledge from ai/prompts/irules_system.md
Read both iRule files (the user should provide two file paths)

Run context analysis on both files:

uv run --no-dev python ai/claude/tcl_ai.py context $FILE_A
uv run --no-dev python ai/claude/tcl_ai.py context $FILE_B

If the analysis tool fails on either file, fall back to manual source comparison and note that LSP analysis was unavailable
Compare the two versions and explain:
- Semantic changes -- What changed in behaviour (not just line diffs)?
- Events -- Any events added, removed, or reordered?
- Security implications -- Do the changes introduce or fix security issues?
- Performance implications -- Any changes to hot-path efficiency?
- Breaking changes -- Could these changes affect traffic handling?
If the user asked a specific question about the diff, focus on that

Output format

Focus on what matters operationally. Be concise. Use headings for each analysis section.

$ARGUMENTS

Mehr aus diesem Repository

gleiches Repository

bytecode-compare

bitwisecook/tcl-lsp

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.

2026-07-0556

compiler-explorer

bitwisecook/tcl-lsp

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.

2026-07-0556

fetch-tcl-source

bitwisecook/tcl-lsp

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.

2026-07-0556

fuzz-findings

bitwisecook/tcl-lsp

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.

2026-07-0556

lsp-client

bitwisecook/tcl-lsp

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.

2026-07-0556

test-results

bitwisecook/tcl-lsp

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.

2026-07-0556

name	irule-diff
description	Compare two iRule versions and explain the semantic differences, security implications, performance changes, and breaking changes. Uses LSP context analysis on both files. Use when comparing iRule versions, diffing F5 iRules, analysing iRule change impact, or reviewing iRule modifications.
allowed-tools	Bash, Read

iRule Diff

Compare two iRule versions and analyse the differences.

Steps

Read the domain knowledge from ai/prompts/irules_system.md
Read both iRule files (the user should provide two file paths)

Run context analysis on both files:

uv run --no-dev python ai/claude/tcl_ai.py context $FILE_A
uv run --no-dev python ai/claude/tcl_ai.py context $FILE_B

If the analysis tool fails on either file, fall back to manual source comparison and note that LSP analysis was unavailable
Compare the two versions and explain:
- Semantic changes -- What changed in behaviour (not just line diffs)?
- Events -- Any events added, removed, or reordered?
- Security implications -- Do the changes introduce or fix security issues?
- Performance implications -- Any changes to hot-path efficiency?
- Breaking changes -- Could these changes affect traffic handling?
If the user asked a specific question about the diff, focus on that

Output format

Focus on what matters operationally. Be concise. Use headings for each analysis section.

$ARGUMENTS