Prompt file imported from dooop/scummvm (.github/prompts/diagnose-build-failure.prompt.md). Copyright stays with the author.

Skill: Diagnose a build failure

Name: diagnose-build-failure
Author: dooop

Use this skill to triage a build failure before attempting any fix. Jumping to a fix without classification leads to wrong or oversized changes.

Step 1: Capture the exact error

Collect the full error text, including:

File path and line number
Error code (e.g. error:, linker command failed, no such module)
Any notes or context lines that follow

Step 2: Classify the error

Class	Indicators	Typical fix
Missing header	`'Foo.h' file not found`	Add search path flag in `Package.swift`
Excluded file needed	Source file cannot be found at link time	Remove wrong exclusion from `Package.swift`
Excluded file conflict	Duplicate symbol or ODR violation	Add exclusion for the conflicting file
Compiler flag missing	Feature macro not defined, C++ standard mismatch	Add `-D` or `-std=` flag to `cxxSettings`/`cSettings`
Swift/ObjC++ interop	`cannot find type`, `use of undeclared identifier` in bridging	Fix or add a header in the relevant `include/` directory
Linker error	`Undefined symbol`, `framework not found`	Add missing xcframework or dependency to target
Concurrency/Swift 6	`Sendable`, `actor isolation` errors	Fix in glue code only; do not change upstream
Upstream source bug	Error inside `scummvm/` that cannot be fixed by flags	Use the `create-engine-override` skill

Step 3: Apply the fix in order of preference

Package.swift only (flag, exclusion, path) — no source change.
Glue code change (swift/Sources/ScummVMiOS/, swift/Sources/ScummVMmacOS/, swift/Sources/ScummVMtvOS/, or swift/Sources/ScummVM/).
Engine override — use the create-engine-override skill.

Never skip to step 3 without first confirming steps 1 and 2 cannot resolve the error.

Step 4: Verify the fix is scoped correctly

The fix touches only files in the allowed edit surface (see copilot-instructions).
No file under scummvm/ has been modified.
The same error does not reappear on a clean build.

Output format when reporting a diagnosis

Error class: <class from table>
File: <path>:<line>
Root cause: <one sentence>
Proposed fix: <location and nature of change>

# Skill: Diagnose a build failure Use this skill to triage a build failure before attempting any fix. Jumping to a fix without classification leads to wrong or oversized changes. ## Step 1: Capture the exact error Collect the full error text, including: - File path and line number - Error code (e.g. `error:`, `linker command failed`, `no such module`) - Any notes or context lines that follow ## Step 2: Classify the error | Class | Indicators | Typical fix | |---|---|---| | Missing header | `'Foo.h' file not found` | Add search path flag in `Package.swift` | | Excluded file needed | Source file cannot be found at link time | Remove wrong exclusion from `Package.swift` | | Excluded file conflict | Duplicate symbol or ODR violation | Add exclusion for the conflicting file | | Compiler flag missing | Feature macro not defined, C++ standard mismatch | Add `-D` or `-std=` flag to `cxxSettings`/`cSettings` | | Swift/ObjC++ interop | `cannot find type`, `use of undeclared identifier` in bridging | Fix or add a header in the relevant `include/` directory | | Linker error | `Undefined symbol`, `framework not found` | Add missing xcframework or dependency to target | | Concurrency/Swift 6 | `Sendable`, `actor isolation` errors | Fix in glue code only; do not change upstream | | Upstream source bug | Error inside `scummvm/` that cannot be fixed by flags | Use the `create-engine-override` skill | ## Step 3: Apply the fix in order of preference 1. `Package.swift` only (flag, exclusion, path) — no source change. 2. Glue code change (`swift/Sources/ScummVMiOS/`, `swift/Sources/ScummVMmacOS/`, `swift/Sources/ScummVMtvOS/`, or `swift/Sources/ScummVM/`). 3. Engine override — use the `create-engine-override` skill. Never skip to step 3 without first confirming steps 1 and 2 cannot resolve the error. ## Step 4: Verify the fix is scoped correctly - The fix touches only files in the allowed edit surface (see copilot-instructions). - No file under `scummvm/` has been modified. - The same error does not reappear on a clean build. ## Output format when reporting a diagnosis ``` Error class: <class from table> File: <path>:<line> Root cause: <one sentence> Proposed fix: <location and nature of change> ```

{ "prompt": "# Skill: Diagnose a build failure\n\nUse this skill to triage a build failure before attempting any fix. Jumping to a\nfix without classification leads to wrong or oversized changes.\n\n## Step 1: Capture the exact error\n\nCollect the full error text, including:\n- File path and line number\n- Error code (e.g. `error:`, `linker command failed`, `no such module`)\n- Any notes or context lines that follow\n\n## Step 2: Classify the error\n\n| Class | Indicators | Typical fix |\n|---|---|---|\n| Missing header | `'Foo.h' file not found` | Add search path flag in `Package.swift` |\n| Excluded file needed | Source file cannot be found at link time | Remove wrong exclusion from `Package.swift` |\n| Excluded file conflict | Duplicate symbol or ODR violation | Add exclusion for the conflicting file |\n| Compiler flag missing | Feature macro not defined, C++ standard mismatch | Add `-D` or `-std=` flag to `cxxSettings`/`cSettings` |\n| Swift/ObjC++ interop | `cannot find type`, `use of undeclared identifier` in bridging | Fix or add a header in the relevant `include/` directory |\n| Linker error | `Undefined symbol`, `framework not found` | Add missing xcframework or dependency to target |\n| Concurrency/Swift 6 | `Sendable`, `actor isolation` errors | Fix in glue code only; do not change upstream |\n| Upstream source bug | Error inside `scummvm/` that cannot be fixed by flags | Use the `create-engine-override` skill |\n\n## Step 3: Apply the fix in order of preference\n\n1. `Package.swift` only (flag, exclusion, path) — no source change.\n2. Glue code change (`swift/Sources/ScummVMiOS/`, `swift/Sources/ScummVMmacOS/`,\n `swift/Sources/ScummVMtvOS/`, or `swift/Sources/ScummVM/`).\n3. Engine override — use the `create-engine-override` skill.\n\nNever skip to step 3 without first confirming steps 1 and 2 cannot resolve the\nerror.\n\n## Step 4: Verify the fix is scoped correctly\n\n- The fix touches only files in the allowed edit surface (see copilot-instructions).\n- No file under `scummvm/` has been modified.\n- The same error does not reappear on a clean build.\n\n## Output format when reporting a diagnosis\n\n```\nError class: <class from table>\nFile: <path>:<line>\nRoot cause: <one sentence>\nProposed fix: <location and nature of change>\n```", "variables": [], "notes": "Use this skill to triage a build failure before attempting any fix. Jumping to a fix without classification leads to wrong or oversized changes.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/dooop/scummvm", "path": ".github/prompts/diagnose-build-failure.prompt.md", "ref": "4a385d6a5ef1aa7b37c2785b467193b1d4dabce0", "url": "https://github.com/dooop/scummvm/blob/4a385d6a5ef1aa7b37c2785b467193b1d4dabce0/.github/prompts/diagnose-build-failure.prompt.md", "key": "dooop/scummvm/.github/prompts/diagnose-build-failure.prompt.md" } } }

diagnose-build-failure

About

Skill: Diagnose a build failure

Step 1: Capture the exact error

Step 2: Classify the error

Step 3: Apply the fix in order of preference

Step 4: Verify the fix is scoped correctly

Output format when reporting a diagnosis

Use it

Manifest

Reviews