amiport

Capture a lesson learned from a porting session and route it to the right enforcement mechanism. Use when a bug, mistake, or process failure occurs that should be prevented in future sessions.

Publish a news entry to the amiport site. Appends to site/data/news.json, validates, deploys via site-manager, and clears the activity cache. Use when announcing a release, project update, milestone, or behind-the-scenes note.

Analyze C source code for Amiga portability issues. Scans headers, system calls, and language features to produce a structured porting report. Use when starting a new port or evaluating whether a project can be ported.

Transform C source code for Amiga compatibility. Replaces POSIX calls with Amiga equivalents or posix-shim wrappers. Use after analyze-source has identified issues.

Dispatch multiple ports from the catalog in parallel using specialized agents. Runs the same pipeline stages as /port-project but overlaps them across ports for ~3x throughput.

Port an entire C project to AmigaOS. Runs the full pipeline — analyze, transform, build, test, package. Use to port a new project from scratch.

Show comprehensive status of a single port — build, tests, reviews, catalog, site data, documentation

Add a new POSIX function to the amiport shim (Tier 1) or emulation (Tier 2) library. Researches AmigaOS APIs first, then implements with proper mapping. Looks up the POSIX spec, classifies the tier, writes the implementation + header + test, and rebuilds the library.

Dispatch the next ready porting candidate from the catalog. Session-resilient — dispatches ONE port per invocation. Re-run to continue the batch.

Print the porting tech tree catalog dashboard — readiness tier distribution, top shim unlock opportunities, and next batch recommendation.

Test compiled Amiga binaries using vamos (virtual AmigaOS runtime). Verifies correct execution and output comparison. Use after a successful build.

Cross-compile C source for Amiga using bebbo-gcc or VBCC in Docker. Manages compiler flags, linking against posix-shim, and packaging. Use after source transformation.

C89/ANSI C language constraints for AmigaOS porting. Use when writing or reviewing C code for this project. Loads the list of C99+ features that are NOT available, libnix function availability, and common mistakes agents make when writing C89 code.

Load the crash patterns knowledge base for AmigaOS debugging. Contains documented crash signatures, root causes, and fixes discovered across all ports. Use when debugging crashes, reviewing code for crash risks, or writing transformations that touch memory/IO/exit paths.

Load the libnix function availability reference. Lists all 700+ functions available in libnix (the -noixemul C runtime), including which are present and which are missing. Use when checking whether a C standard library function is available on AmigaOS, or when a linker reports undefined symbols.

Amiga-specific code review for ported programs. Checks for stack overflow risks, memory allocation patterns, BPTR handling, library cleanup, 68k alignment issues, and AmigaOS conventions. Use after porting or before publishing to Aminet.

Look up AmigaOS API documentation from the ADCD reference library. Use when writing or reviewing code that calls AmigaOS functions (exec.library, dos.library, timer.device, intuition, graphics, etc.), designing shim functions, or needing to understand struct layouts, function signatures, or usage patterns. Also use when designing new AmigaOS-native features like profilers, crash handlers, or device drivers.

Write ARexx scripts for AmigaOS automation, testing, and inter-process communication. Use when creating or modifying .rexx files, writing FS-UAE test harnesses, or automating Amiga workflows.

Debug a crashed Amiga port using Enforcer hit capture and autonomous fix loop. Runs test-fsemu in debug mode, captures crashes, and dispatches the debug-agent to fix them. Use after a port builds but crashes at runtime.