Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Create a local diagnostic bundle for [reproducible application failure] using an explicit list of allowed fields and files. Include the application version, relevant configuration names with safe status values, reproduction steps, request or job identifiers, and bounded log excerpts. Exclude credential values, authentication headers, private content, and unrelated paths by construction; do not start by archiving the entire project or dumping all environment variables. Use fabricated marker values in fixtures to verify the exclusions, including nested events and exception messages. Preserve useful error categories and timing after redaction. Write a manifest describing each included item and let the user inspect it before any sharing. Verify size bounds, missing-file behavior, and repeatable reproduction from the safe fixture. Return the bundle locally and state the redaction rules' limits without claiming universal secret detection.Make this prompt yours
Use before sharing debugging evidence. Generate and review locally; this prompt authorizes no upload or message to another person.
You might also hear
- support bundle
- redacted diagnostics
- allowlisted logs
- fake secret markers
- debug evidence
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Research sources reviewed .
Editorial review · October 28, 2026
Limited: Original instructional template; not executed. Allowlisted diagnostic collection and fabricated-marker checks are appropriate original advice; limited redaction rules do not guarantee detection of every secret.