AI Prompt Reference
Log in
Back to library
DevelopmentGPT-5DebuggingTestingPerformance

Mobile Crash Triage

Turn mobile crash logs into triage and fix plans.

Mobile Crash Triage

Prompt

# Role
You are a mobile stability engineer familiar with crash clustering, device/OS differences, and release rollback.

# Task
Create a triage plan from crash logs and release info below.

# Inputs
Ask me for: background, goal, audience, existing assets, constraints, success criteria, output language, and channel. If data, competitors, screenshot descriptions, or past examples are provided, prioritize those facts and do not invent missing details.

# Output Format
1. Crash summary
2. Impact scope
3. Likely causes
4. Repro path
5. Fix plan
6. Verification and release strategy

# Quality Bar
1. Do not guess without evidence
2. Mark evidence strength
3. Consider staged rollout and rollback

# Avoid
Do not give generic advice. Do not use unverifiable hype. Do not pad with irrelevant completeness. For business, medical, financial, legal, or security risks, state assumptions and boundaries.

# Verification Control
Provide a reusable checklist and explain which missing inputs would significantly change the result.

# Process
First decide whether the information is sufficient. If not, ask up to five clarifying questions. If yes, produce the actionable version directly. End with a concise copy-ready version.

Curated by the editorial team · Updated 06/28/2026 · Model: GPT-5

Usage guide

How to use this prompt

This template is designed for development tasks. Replace the sample details with real constraints before running it in GPT-5.

  1. Step 1

    State the stack, runtime, inputs, outputs, and existing constraints.

  2. Step 2

    Ask for the approach and risks before requesting the smallest verifiable change.

  3. Step 3

    Run tests, type checks, and critical scenarios locally before merging.

Details to replace or add

Specific inputs produce more useful results. Do not submit passwords, private information, or confidential business data.

  • Language, framework, and versions
  • Current code and error output
  • Expected inputs and outputs
  • Compatibility and performance constraints
  • Acceptance test cases

Output checklist

  • The code runs on the specified versions
  • Edge cases and errors are handled
  • Existing project patterns are reused
  • Tests cover critical behavior
  • No new security or performance risk appears

Common adjustments

Provide the directory structure and interfaces when the answer drifts from the project.

Limit files and request staged changes when the proposal is too broad.

Ask for runnable test commands and expected output when verification is unclear.

This prompt separates Development, Debugging, Testing, Performance requirements into context, constraints, and output format. Keep the objective fixed and revise only the conditions that failed before rewriting the whole template.

Related prompts

Explore more templates in Development.