oracle

What This Skill Does

The Oracle skill provides an intelligent interface to the @steipete/oracle CLI, enabling users to bundle specific repository files and prompts into a cohesive context for advanced model review. It acts as a bridge to deep code analysis, allowing users to leverage GPT-5.2 Pro via browser automation or API to perform debugging, refactoring, design critiques, and cross-validation tasks. By automatically managing context window optimization and file exclusion patterns, it ensures that external models receive exactly the relevant information needed to solve complex programming tasks.

Installation

To integrate this skill into your OpenClaw environment, use the following command: clawhub install openclaw/skills/skills/steipete/oracle

Use Cases

• Complex Refactoring: Provide a set of interdependent files and ask the agent to suggest architectural improvements or modernizations.
• Debugging: When local testing fails to reveal the root cause, bundle the suspected files and request a second-model review to identify logic errors or race conditions.
• Design Checks: Compare current implementation patterns against project standards or documentation to ensure consistency across the codebase.
• Knowledge Transfer: Generate an explanation of how a specific, complex module functions by sending the source files and asking for a high-level architectural walkthrough.

Example Prompts

1. "Oracle, look at the files in src/auth and src/middleware, then suggest how to refactor them to support role-based access control without duplicating logic."
2. "I am getting a cryptic memory leak in src/engine.ts. Please analyze the relevant files and suggest why my current approach might be failing."
3. "Run a dry-run summary for a design check on src/components/ui to see if the file set is too large, then proceed with a browser-based review if it looks good."

Tips & Limitations

• Browser-First: Always favor --engine browser for complex tasks; it facilitates a persistent session that can be reattached if disconnected.
• File Filtering: Be intentional with your inclusions. The tool honors .gitignore and ignores common build artifacts like node_modules automatically, but explicit filtering helps keep your context tight.
• Size Constraints: Keep individual file contributions under 1MB. If you hit a hard limit, break your request down into smaller, more granular module analysis.
• Human-in-the-loop: Oracle is advisory. Always review, verify, and run tests against any suggestions provided before merging them into your main branch.