codex-result-handling

Consolidate Codex companion outputs into auditable result packages.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/mrkhachaturov/rkstack --skill codex-result-handling-mrkhachaturov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-result-handling
Source: https://github.com/mrkhachaturov/rkstack/tree/main/skills/codex-result-handling
Command: npx skills add https://github.com/mrkhachaturov/rkstack --skill codex-result-handling-mrkhachaturov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internal contract for presenting Codex output back to the user. Referenced by dual-review (structured findings) and rescue (task output). Not user-invocable.

Core Features & Use Cases

  • Defines a stable schema for Codex outputs, preserving verdicts, summaries, findings, and next steps.
  • Enables auditable handoffs between Codex-assisted reviews and downstream tasks.
  • Supports repeatable review workflows in dual-review and rescue scenarios.

Quick Start

Refer to the Codex companion output and apply its verdict, summary, findings, and next steps to guide your review workflow.

Frequently Asked Questions about codex-result-handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Codex findings for an auditable review workflow?

Codex findings are consolidated into an auditable result package that preserves verdicts, summaries, findings, and next steps. This fixed schema ensures predictable, traceable handoffs between Codex-assisted reviews and downstream tasks.

What is a Codex result handling contract and when do I need it for dual-review?

A Codex result handling contract defines a stable schema for presenting review outputs. You need it during dual-review and rescue workflows to enforce a predictable, traceable structure for verdicts, summaries, findings, and next steps.

How do I preserve Codex verdicts to prevent unintended alterations during reviews?

Codex verdicts are preserved by enforcing a fixed contract with a read-only presentation of verdict, summary, findings, and next steps. This prevents unintended alterations and maintains auditable handoffs between review tasks.

Can I use Codex result handling for rescue workflows alongside dual-review scenarios?

Yes, Codex result handling applies to both dual-review and rescue workflows. It consolidates companion outputs into an auditable result package, ensuring a predictable, traceable structure for task outputs and structured findings.

Does the Codex review workflow result schema support downstream task handoffs?

The Codex review workflow result schema supports downstream task handoffs by consolidating companion outputs into an auditable package. It defines a stable structure for verdicts, summaries, findings, and next steps to guide reviews.