codex-result-handling

Code analysis output formatting requires structuring findings by severity, preserving exact file paths and line numbers, and maintaining distinctions between inferences and uncertainties to ensure technical documentation accuracy. The skill handles this by presenting ordered findings with verdicts, summaries, and next steps.

Presenting Codex helper results involves maintaining the integrity of findings and recommendations through structured output. The process targets technical documentation review workflows by adhering to the helper's output structure and maintaining user context throughout the presentation.

Handling failed or incomplete Codex runs requires appropriate session handling that avoids substituting with Claude-side implementations. The skill ensures output presentation maintains the helper's original structure without fabricating missing findings or generating synthetic replacements.

Yes, codex-result-handling targets both technical documentation review and code analysis workflows. It structurally presents helper output by adhering to the output structure, maintaining user context, and ensuring clarity and accuracy in findings presentation across both use cases.

Losing evidence distinctions happens when output formatting collapses inferences, uncertainties, and follow-up questions into undifferentiated text. The skill addresses this by explicitly preserving these categories in the structured presentation of findings and recommendations.

A structured code analysis report should include the helper's verdict, summary, findings ordered by severity, and next steps. It must use exact file paths and line numbers as reported by the helper while preserving distinctions between inferences, uncertainties, and follow-up questions.