oracle

Query Codex for external architectural review in a tmux window.

2|Updated Aug 1, 2024
One-click install
npx skills add https://github.com/Kabilan108/dotfiles --skill oracle-kabilan108
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oracle
Source: https://github.com/Kabilan108/dotfiles/tree/main/agents/skills/oracle
Command: npx skills add https://github.com/Kabilan108/dotfiles --skill oracle-kabilan108

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, codex, and includes scripts (resource) components.

What problem does it solve?

This skill provides external architectural review by querying Codex to gain a second opinion on difficult bugs, architecture decisions, and tricky implementations. It helps engineers validate approaches and spot issues that might be missed.

Core Features & Use Cases

  • Non-interactive Codex analysis: Launches Codex CLI in a dedicated tmux Oracle window so you can watch progress and capture output for later synthesis.
  • Guided prompting & structured reasoning: Encourages specific, well-scoped questions to yield actionable insights.
  • Use Case: When facing a hard bug or architectural trade-off, invoke the oracle to get a corroborating analysis before proceeding with fixes.

Quick Start

  1. Create a prompt file describing your problem at /tmp/oracle-prompt.txt
  2. Run the oracle runner: eval "$(bash agents/skills/oracle/scripts/oracle-run.sh /tmp/oracle-prompt.txt)"
  3. Wait for the ORACLE_DONE sentinel and read the results from the produced output file (ORACLE_OUT)

Frequently Asked Questions about oracle

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

FAQPage Schema
How do I get a second opinion on a hard debugging problem using Codex?

To get a Codex second opinion on a hard debugging problem, write your issue to a prompt file and execute the oracle-run.sh script, which launches the Codex CLI in a dedicated tmux window to capture and return non-interactive reasoning results.

What is the best way to validate architectural decisions across a codebase?

Validating architectural decisions across a codebase is done by querying Codex for an external architectural review. You create a well-scoped prompt file describing the trade-off, and the skill orchestrates a non-interactive reasoning session to yield actionable insights.

Do I need tmux and the Codex CLI installed to run architectural validation?

Yes, you need tmux and the Codex CLI installed to run architectural validation. The skill operates in a dedicated tmux Oracle window to manage the non-interactive Codex session and requires the oracle-run.sh script to orchestrate prompts and capture output.

How does non-interactive reasoning with Codex work in a tmux window?

Non-interactive reasoning with Codex works by launching the CLI in a dedicated tmux Oracle window. This allows you to watch progress, wait for an ORACLE_DONE sentinel, and read the captured output from a produced file for later synthesis.

What are the limitations of using Codex for code reviews on novel implementations?

The limitation of using Codex for code reviews on novel implementations is that it requires specific, well-scoped questions to yield actionable insights. It operates non-interactively via a tmux session, meaning it cannot dynamically ask clarifying questions during the architectural review process.