repo-oracle

Answers historical codebase questions using git log, git blame, and .ai memory files.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Vimurai/ai-os --skill repo-oracle-vimurai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-oracle
Source: https://github.com/Vimurai/ai-os/tree/main/.claude/skills/repo-oracle
Command: npx skills add https://github.com/Vimurai/ai-os --skill repo-oracle-vimurai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When modifying existing code, developers often lack context about why it was built a certain way, when it changed, or which commit introduced a regression. This Skill answers those historical questions by searching git history and project memory files before any code is touched. ## Core Features & Use Cases - Guided Git Archaeology: Runs scoped git log --follow, git blame, and date-filtered history queries to trace when and why code changed. - Project Memory Search: Greps .ai/LOG.md and .ai/DECISIONS.md to surface recorded decisions and the E-## task that produced a file. - Regression Investigation: Locates the commit that introduced a failing test or bug using targeted history queries. - Use Case: Before refactoring a legacy module, ask why it was implemented a certain way and receive the originating commit hash, date, and decision context. ## Quick Start Ask why a specific file or function works the way it does and request the commit and decision history behind it.

Frequently Asked Questions about repo-oracle

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

FAQPage Schema
How do I find out why code was written a certain way?▼

Search the project's decision records with grep against .ai/LOG.md and .ai/DECISIONS.md for relevant keywords, then run git log --follow on the file to see its change history. This reveals the reasoning and the commit that introduced the behavior.

How to find which commit introduced a bug or regression?▼

Use git log --oneline --follow -p on the affected file to see recent changes, or filter by date with git log --since to narrow the window. For test failures, check the history of both the test file and the source file it covers.

Can git blame show who wrote a specific line of code?▼

Yes, git blame -L start,end on a file shows the author and commit for each line in the given range. This skill uses it to attribute specific lines to their originating commits.

Does this skill modify code based on history findings?▼

No, it is strictly read-only. It reports findings with commit hash, date, and source, and explicitly does not modify any file based on historical analysis.

What are the limitations of git history search for large repos?▼

The skill caps reads at 3 files per query, prefers grep over full file reads, and asks users to narrow queries if an answer requires more than 60 lines of git log output. It also avoids unscoped git log and node_modules history.