SweetClaude Report Failure

To generate a structured incident report, invoke the skill to document the deployment failure, which produces a consistent Markdown report including incident datetime, technical mechanisms, and impact within the .sweetclaude/failure/ directory.

The best way to perform root cause analysis for development incidents is using a structured 5-whys methodology, which guides you through iterative questioning to identify the underlying source of the failure accurately without relying on vague memory.

Yes, you need git integration to document project post-mortems because the skill requires git SHAs and timestamps to verify repository history, ensuring reports are evidence-based and anchored in verifiable commit data for accurate incident reconstruction.

Evidence-based reporting improves software failure traceability by enforcing the use of git SHAs, timestamps, and file paths, which anchors incident documentation in verifiable repository history and maintains a traceable record of project mistakes and corrections.

You should use a standardized post-mortem format for incident reporting whenever a project mistake or failure occurs, ensuring lessons are captured accurately and consistently to prevent recurrence and maintain a traceable history of corrections.