Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

crash-patterns

Sterne28

Forks2

Aktualisiert23. März 2026 um 13:56

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.

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

bdgscotland

bdgscotland/amiport

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	crash-patterns
description	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.

Crash Patterns Knowledge Base

Load the crash patterns reference before debugging, transforming, or reviewing code.

Read the file docs/references/crash-patterns.md now. It contains:

Numbered crash patterns with signatures, root causes, and fixes
vamos vs real hardware behavior differences
Common misdiagnoses and their actual root causes
ARexx/FS-UAE testing pitfalls

Every pattern in this file was discovered from a real bug in a real port. Check against it before:

Writing exit/cleanup code (patterns #5, #9)
Handling file I/O (pattern #12)
Using stack-heavy functions (patterns #7, #10)
Writing test harnesses (pattern #9)
Using vsnprintf (pattern #5)
Mixing amiport_open with fdopen (pattern #12)
Using MB_CUR_MAX in conditionals (pattern #11)

Mehr aus diesem Repository

gleiches Repository

capture-learning

bdgscotland/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.

2026-04-1428

post-news

bdgscotland/amiport

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.

2026-04-1328

analyze-source

bdgscotland/amiport

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.

2026-04-1328

transform-source

bdgscotland/amiport

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

2026-04-1328

batch-port-parallel

bdgscotland/amiport

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.

2026-04-1228

port-project

bdgscotland/amiport

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

2026-04-1228

name	crash-patterns
description	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.

Crash Patterns Knowledge Base

Load the crash patterns reference before debugging, transforming, or reviewing code.

Read the file docs/references/crash-patterns.md now. It contains:

Numbered crash patterns with signatures, root causes, and fixes
vamos vs real hardware behavior differences
Common misdiagnoses and their actual root causes
ARexx/FS-UAE testing pitfalls

Every pattern in this file was discovered from a real bug in a real port. Check against it before:

Writing exit/cleanup code (patterns #5, #9)
Handling file I/O (pattern #12)
Using stack-heavy functions (patterns #7, #10)
Writing test harnesses (pattern #9)
Using vsnprintf (pattern #5)
Mixing amiport_open with fdopen (pattern #12)
Using MB_CUR_MAX in conditionals (pattern #11)