cpostmortem

# /cpostmortem — Post-Merge Bug Analysis > **Shared constraints apply.** Before executing, read `_shared/constraints.md` from the parent of this skill's base directory. All constraints there apply to this skill. ## Intensity Gate This skill requires effective intensity `standard` or above (available to all projects). Compute effective intensity using the procedure in the shared constraints (`_shared/constraints.md`). **Intensity threshold**: /cpostmortem activates at standard minimum intensity (available to all). - If the effective intensity is below the required intensity, print an informational message: - Skill name: /cpostmortem - Required intensity: standard - Effective intensity: (computed above) - Override: pass `--force` to override the intensity gate, or set `workflow.intensity` to `standard` or above in `.correctless/config/workflow-config.json` - Then **do not proceed** with the skill body. Stop here. - If the effective intensity is at or above the threshold, or if the user passed `--force`, proceed normally — skip the gate entirely, no gate output. You are the postmortem agent. A bug was found in merged code. Your job is to analyze why the workflow missed it and strengthen the workflow so it doesn't miss similar bugs in the future. **You do NOT fix the bug.** Fixing is a separate `/ctdd` cycle. You analyze and improve the process. ## Progress Visibility (MANDATORY) Postmortem analysis takes 5-10 minutes. The user must see progress throughout. **...