review-amiga

Analyze ported C code for AmigaOS correctness and generate a structured report.

30|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/bdgscotland/amiport --skill review-amiga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-amiga
Source: https://github.com/bdgscotland/amiport/tree/main/.claude/skills/review-amiga
Command: npx skills add https://github.com/bdgscotland/amiport --skill review-amiga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Amiga-specific code review ensures ported C programs adhere to AmigaOS conventions, avoid stack and memory issues, and prevent resource leaks that standard reviews might miss.

Core Features & Use Cases

  • Stack safety checks tailored to AmigaOS (4KB default stack, chip vs fast RAM considerations) and detection of deep recursion.
  • Memory management and cleanup verification, including AllocMem/AllocVec usage, memory leaks, and proper FreeVec/FreeMem release across error paths.
  • BPTR handling and file/dir lifecycle checks, ensuring proper Lock/UnLock, Open/Close, and CurrentDir restoration.
  • AmigaOS library protocol and version checks, ensuring libraries are opened/closed and compatibility is respected.
  • AmiPort shim usage and adherence to conventions, including instrumentation comments and correct wrapper usage.
  • Platform compatibility checks for 68k alignment, endianness, and struct alignment pitfalls.

Quick Start

Run the Amiga code review on the ported source located at the provided path to obtain a structured, actionable report.

Frequently Asked Questions about review-amiga

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

FAQPage Schema
How do I review ported C code for AmigaOS memory leaks and stack safety?

To review ported C code for AmigaOS memory leaks and stack safety, analyze AllocMem and AllocVec usage across error paths to verify proper FreeMem and FreeVec release. Stack safety checks verify 4KB default limits and detect deep recursion to prevent crashes.

What is BPTR handling and why does it matter for AmigaOS porting?

BPTR handling in AmigaOS porting involves verifying proper Lock and UnLock lifecycle management for files and directories. Correct BPTR handling ensures CurrentDir restoration and prevents resource leaks that standard code reviews might miss.

How do I check 68k alignment and endianness issues in Amiga ported source code?

To check 68k alignment and endianness issues in Amiga ported source code, analyze struct alignment pitfalls and platform compatibility constraints. This review verifies that memory access patterns respect 68k alignment requirements and endianness differences.

Can I use an AmigaOS code review to verify library protocol and version compatibility?

Yes, AmigaOS code review verifies library protocol and version compatibility by checking that libraries are properly opened and closed. This ensures compatibility is respected and library version checks conform to AmigaOS conventions.

What does an Amiga readiness score include in a ported code review report?

An Amiga readiness score in a ported code review report summarizes correctness across stack safety, memory allocation, BPTR handling, and amiport shim usage. The structured report includes critical issues, warnings, improvement suggestions, and a safety assessment.

Why does my AmigaOS port crash when using amiport shims with deep recursion?

AmigaOS port crashes with amiport shims and deep recursion often stem from exceeding the 4KB default stack limit. Stack safety checks detect deep recursion patterns and verify amiport shim wrapper usage to prevent stack overflow on AmigaOS.