review-mcode

Identify MCode optimization opportunities for hot loops in AutoHotkey scripts.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill review-mcode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-mcode
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/review-mcode
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill review-mcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies performance bottlenecks in AutoHotkey scripts, specifically targeting hot loops that can be significantly accelerated by compiling them into native C code (MCode).

Core Features & Use Cases

  • Hot Loop Identification: Pinpoints frequently called or data-scaling loops that are interpreter-bound.
  • MCode Optimization: Recommends replacing pure buffer computations with efficient native C implementations.
  • Use Case: Analyze a script that processes large image buffers pixel-by-pixel; identify the loop as a candidate for MCode optimization to achieve substantial speedups.

Quick Start

Scan the codebase for MCode optimization opportunities and generate a plan.

Frequently Asked Questions about review-mcode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize slow AutoHotkey loops with native C?▼

You can optimize slow AutoHotkey loops by identifying interpreter-bound hot loops and replacing them with MCode (native C). This targets pure buffer computations exceeding a ~100μs worst-case cost for substantial speedups.

How does MCode optimization work for AutoHotkey scripts?▼

MCode optimization works by compiling hot loops into native C code to bypass the AutoHotkey interpreter. It scans for math-heavy loops and NumGet/NumPut buffer iterations, recommending native C replacements.

When do I need MCode for AutoHotkey performance bottlenecks?▼

You need MCode for AutoHotkey performance bottlenecks when pure buffer computations scale with data and exceed a ~100μs worst-case cost, such as processing large image buffers pixel-by-pixel.

Can I use native C optimization for byte-by-byte buffer iteration in AutoHotkey?▼

Yes, you can use native C optimization for byte-by-byte buffer iteration in AutoHotkey. It analyzes codebases for NumGet/NumPut within loops and flags data-scaling candidates for MCode acceleration.

What are the limitations of MCode optimization in AutoHotkey?▼

MCode optimization in AutoHotkey is limited to pure buffer computations and math-heavy loops. It targets interpreter-bound hot loops exceeding ~100μs, meaning non-computational bottlenecks or UI-bound scripts are not suitable candidates.