consult-oracle
The consult-oracle skill automates browser-based consultation with ChatGPT Pro through Chrome, designed for debugging scenarios where standard troubleshooting has failed. It requires pre-configured ChatGPT access via Chrome profile, cookie refresh via Python script, identification of relevant source files, and execution of a Python oracle runner that sends problem descriptions to ChatGPT and persists responses for analysis and synthesis against official documentation.
git clone --depth 1 https://github.com/tobihagemann/turbo /tmp/consult-oracle && cp -r /tmp/consult-oracle/claude/skills/consult-oracle ~/.claude/skills/consult-oracleSKILL.md
# Consult Oracle
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.
## Configuration
The oracle reads from `~/.turbo/config.json`:
```json
{
"oracle": {
"chatgptUrl": "https://chatgpt.com/",
"chromeProfile": "Default"
}
}
```
| Key | Purpose | Default |
|---|---|---|
| `chatgptUrl` | ChatGPT URL (e.g., a custom GPT project URL) | `https://chatgpt.com/` |
| `chromeProfile` | Chrome profile directory name | `Default` |
## Step 1: Refresh Cookies
Before running the oracle, refresh ChatGPT cookies from Chrome. Requires timeout of 60000ms. A macOS Keychain password prompt will appear for the user.
```bash
python3 scripts/refresh_cookies.py
```
If the script reports session validation failure, the user needs to log into ChatGPT in Chrome first.
## Step 2: Identify Key Files
Find the 2-5 files most relevant to the problem.
## Step 3: Formulate the Question
Write a clear, specific problem description. Include what has already been tried and why it failed. Open with a short project briefing (stack, services, build steps). The more context, the better the response.
## Step 4: Run the Oracle
Run via the Bash tool (`timeout: 3600000`, do not set `run_in_background`). The script loads `chatgptUrl` from `~/.turbo/config.json` automatically. Generate a random tag and persist the response:
```bash
ORACLE_TAG=$(head -c 4 /dev/urandom | xxd -p) && mkdir -p .turbo/oracle
python3 scripts/run_oracle.py --prompt "<problem description>" --file <relevant files...> --write-output ".turbo/oracle/$ORACLE_TAG.txt"
```
## Step 5: Synthesize
Read the response from `.turbo/oracle/$ORACLE_TAG.txt`. Summarize the key insights from the consultation. Cross-reference suggestions with official docs and peer open-source implementations before applying. Oracle suggestions are starting points, not guaranteed solutions.For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to \"answer reviewer questions\", \"draft answers to PR questions\", or \"explain reviewer questions\".
Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to \"apply findings\", \"apply fixes\", \"apply suggestions\", \"apply accepted findings\", \"fix the findings\", or \"apply the review results\".
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to \"audit the project\", \"run a full audit\", \"project health check\", \"audit my code\", \"codebase audit\", or \"comprehensive review\".
Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.
Enforce mirror, reuse, and symmetry principles to keep new code consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.
Run autonomous task execution using the codex CLI. Use when the user asks to \"codex exec\", \"run codex exec\", \"execute a task with codex\", or \"delegate to codex\".
Run AI-powered code review using the codex CLI. Use when the user asks to \"codex review\", \"run codex review\", or \"review a commit with codex\".
Shared commit message rules and technical constraints referenced by $stage-commit and $commit-staged. Not typically invoked directly.