Claude Code prompt

Claude Code Ship: Incident Follow-Up

Turn an incident into durable engineering actions with repository-aware safeguards.

Best tool
Claude Code
Difficulty
Advanced
Use case
Incident Follow-Up
Prompt type
Reusable prompt

What this prompt does

Turn an incident into durable engineering actions with repository-aware safeguards. It is designed for incident follow-up and works best with Current Claude Code model configured for the repository.

Copy-ready prompt

This is a reusable natural-language prompt for Claude Code, not a shell command. Work in the repository at [REPOSITORY_OR_PATH]. Goal: turn an incident into durable engineering actions. Context: [CONTEXT]. Constraints: [CONSTRAINTS]. Definition of done: [ACCEPTANCE_CRITERIA]. Run relevant checks, summarize the diff, call out risks and rollback, and prepare reviewer-facing notes. Read applicable CLAUDE.md guidance and use Claude Code’s repository tools and permission model; do not assume an interactive slash command or CLI flag is available. First read the repository instructions and relevant framework documentation. Preserve unrelated user changes. State assumptions, cite files and lines for findings, and ask only when a missing decision would materially change the result. Do not invent APIs, commands, flags, test results, or file contents. Deliver: timeline, contributing factors, fixes, and prevention. Run the repository’s relevant formatting, lint, type, test, and build checks when authorized, and report exact results.

How to use it

Replace the bracketed variables with real context for incident follow-up. Attach or paste source material when available, and verify consequential facts before acting.

#claude-code#software-engineering#incident-follow-up#ship

Related prompts