skills.rest
cwilliams5
cwilliams5COMMUNITY
Explore all skills by this author →
Website𝕏@codywilliamsGitHub

review-ahk2

Scans AutoHotkey v2 source code for legacy v1 patterns and syntax errors.

1|Updated Jan 12, 2026
Search Tags:#quality assurance#static analysis#code review#scripting#autohotkey#v2 migration
One-click install
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill review-ahk2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-ahk2
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/review-ahk2
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill review-ahk2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and flags legacy AutoHotkey v1 patterns that may have inadvertently slipped into an AutoHotkey v2 codebase, preventing subtle bugs and ensuring adherence to v2 best practices.

Core Features & Use Cases

  • Pattern Detection: Scans source code for common v1 syntax and command structures that are deprecated or behave differently in v2.
  • Migration Assistance: Helps developers maintain code quality during AI-assisted development by catching v1 habits.
  • Use Case: After AI-assisted code generation for an AutoHotkey v2 project, use this Skill to perform a thorough review, ensuring that no v1-specific syntax like %variable% dereferencing or v1 command formats (e.g., MsgBox, text) have been introduced.

Quick Start

Scan all source files for AutoHotkey v1 patterns that do not belong in a v2 codebase.

Frequently Asked Questions about review-ahk2

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

FAQPage Schema
How do I check AutoHotkey v2 code for legacy v1 syntax patterns?▼

To check AutoHotkey v2 code for legacy v1 syntax, scan the source files to identify deprecated command structures like MsgBox, text or %variable% dereferencing. This ensures adherence to v2 best practices and prevents subtle bugs.

What are common AutoHotkey v1 patterns that break v2 scripts?▼

Common AutoHotkey v1 patterns that break v2 scripts include legacy command syntax, incorrect variable scope handling, and outdated object model implementations. Scanning detects these deprecated structures to maintain v2 code quality.

How do I review AI-generated AutoHotkey code for v1 migration mistakes?▼

Review AI-generated AutoHotkey code by scanning for v1-specific syntax and command formats inadvertently introduced during generation. This catches legacy habits and ensures the output strictly follows v2 best practices.

Does AutoHotkey v2 static analysis detect incorrect function usage and variable scope?▼

AutoHotkey v2 static analysis detects incorrect function usage and variable scope by scanning source code against a comprehensive checklist. It identifies common mistakes in syntax and object model implementation derived from migration guides.

What is the best way to ensure AutoHotkey v2 code quality during a v2 migration?▼

The best way to ensure AutoHotkey v2 code quality during migration is scanning source files for legacy v1 patterns. This enforces adherence to v2 best practices by flagging deprecated syntax and common migration mistakes.

When do I need to scan AutoHotkey source files for deprecated command structures?▼

Scan AutoHotkey source files for deprecated command structures when maintaining code quality during AI-assisted development or v2 migration. This prevents subtle bugs caused by inadvertently introducing v1-specific syntax.

Related Skills

Explore More Software Engineering Skills→
alexFrankfurtalexFrankfurt

windeskapp-ahk-tools

Execute AutoHotkey v2 scripts to focus, screenshot, and type fractions in windeskapp.

Community
Basic
JoaquinCampoJoaquinCampo
3

pydantic

Enforce Pydantic v2 patterns with ConfigDict and modern validators.

Community
Intermediate
robertbr123robertbr123

requesting-code-review

Automate code review with security scans, quality checks, and automated fixes.

Community
Advanced
BetaSBetaS

code-review

Review source code changes for security, quality, and maintainability issues.

Community
Advanced