trace

Search Git history, local repositories, and Oracle memory for project traces.

116|56|Updated Jan 18, 2026

Search Tags:#discovery #memory #trace #git history #repositories #ghq

Ready to run

npx skills add https://github.com/Soul-Brews-Studio/oracle-skills-cli --skill trace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/Soul-Brews-Studio/oracle-skills-cli/tree/main/src/skills/trace
Command: npx skills add https://github.com/Soul-Brews-Studio/oracle-skills-cli --skill trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables fast, unified discovery of project information by tracing across git history, local repositories, and Oracle memory.

Core Features & Use Cases

Unified search across repos: locate projects by name, code, or related files in current or remote repositories.
Trace logging: generate time-stamped trace logs that become part of Oracle memory for future queries.
Flexible modes: use --oracle for quick results, --smart for balanced depth, or --deep for thorough multi-agent searches.
Repo targeting: search the current repo, a specified path, or clone a remote URL via ghq for trace.

Quick Start

Run a trace for your query in the current repository: /trace [query] Or search a remote with a URL: /trace [query] --repo [url] To switch modes, add --oracle, --smart, or --deep as needed.

Frequently Asked Questions about trace

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

FAQPage Schema

How do I find a project across multiple git repositories and local codebases?▼

You can search across git repositories by running a trace query with a project name or code snippet. It scans current local paths, git history, and remote URLs, consolidating results into a structured log for future reference.

What's the best way to search a remote git repository for specific code history?▼

The best way to search a remote repository is using the --repo flag with a URL. The tool clones the target via ghq and executes a trace across its commit history and project files to locate the requested query.

Can I use ghq to target specific remote repositories for code discovery?▼

Yes, you can use ghq to target remote repositories for code discovery. By providing a remote URL with the --repo flag, the system uses ghq to clone and trace the specified repository's history and structure.

How do I log search results into Oracle memory for future queries?▼

You log search results into Oracle memory by executing a trace query, which automatically generates time-stamped trace logs. These logs are saved into ψ memory, making consolidated results available for future queries.

Does trace support different search depths for git history and local repositories?▼

Yes, trace supports different search depths for git history and local repositories. You can use the --oracle mode for quick results, --smart for balanced depth, or --deep for thorough multi-agent searches across all sources.

When should I use the deep search mode instead of the quick oracle mode?▼

You should use deep search mode instead of quick oracle mode when you need thorough multi-agent searches across complex git history and remote repositories. Use --oracle for quick lookups and --deep for comprehensive discovery.