Code Oracle

A mystical fortune-teller that reads your codebase's future using real metrics disguised as prophecies. Tarot-style readings, crystal ball predictions, and zodiac forecasts — all powered by actual data. The prophecy "The Tower will fall in the eastern quarter" means "src/api/ has rising complexity and declining test coverage." Mystically accurate.

"The stars do not predict your destiny. But your commit history does."

What It Does

Code Oracle reads your codebase's fortune — tarot cards drawn from real code metrics, crystal ball predictions powered by trend analysis, horoscopes written from git history patterns. Every prophecy is backed by real data, wrapped in mystical metaphor.

It's metrics reporting for people who'd rather consult a soothsayer than a Grafana dashboard.

The Tarot Reading

Three cards drawn from the Major Arcana of Software Development:

text

╔══════════════════════════════════════════════════════════════╗
║                  🔮 THE CODE ORACLE 🔮                       ║
║              Your Three-Card Reading                         ║
╠══════════════════════════════════════════════════════════════╣
║                                                              ║
║  PAST              PRESENT           FUTURE                  ║
║  ┌──────────┐     ┌──────────┐     ┌──────────┐            ║
║  │          │     │          │     │          │             ║
║  │ THE TOWER│     │ THE WHEEL│     │ THE STAR │             ║
║  │  (XVI)   │     │  (X)     │     │  (XVII)  │             ║
║  │          │     │          │     │          │             ║
║  │  🏗️→💥   │     │   🎡     │     │    ⭐    │             ║
║  │          │     │          │     │          │             ║
║  │ Upheaval │     │ Change   │     │  Hope    │             ║
║  │          │     │          │     │          │             ║
║  └──────────┘     └──────────┘     └──────────┘            ║
║                                                              ║
║  READING:                                                    ║
║                                                              ║
║  PAST — THE TOWER (Reversed)                                 ║
║  "A great upheaval reshaped the eastern quarter."            ║
║  Data: src/api/ was rewritten 6 weeks ago. 347 lines         ║
║  changed in 3 days. The migration left 4 TODOs and           ║
║  2 skipped tests. The dust has settled, but the              ║
║  foundation was hastily laid.                                 ║
║                                                              ║
║  PRESENT — THE WHEEL OF FORTUNE                              ║
║  "The wheel turns. What was stable grows uncertain."         ║
║  Data: Test flakiness increased 3x this week. CI             ║
║  pipeline takes 40% longer than last month. Change           ║
║  velocity is high but quality metrics are declining.          ║
║  The wheel is spinning fast — but which way?                 ║
║                                                              ║
║  FUTURE — THE STAR                                           ║
║  "After the storm, clarity emerges. A guide appears."        ║
║  Prediction: If the 4 TODOs from the API rewrite are         ║
║  addressed and the flaky tests are stabilized, the           ║
║  codebase enters a period of high productivity.              ║
║  Ignore them, and The Tower returns — this time, upright.    ║
║                                                              ║
║  THE ORACLE ADVISES:                                         ║
║  "Fix the foundation before building higher."                ║
║                                                              ║
╚══════════════════════════════════════════════════════════════╝

The Tarot Deck (Major Arcana of Software)

Card	Upright	Reversed	Data Source
0 The Fool	New project, fresh start, green field	Reckless commit, no tests	New repos, first commits
I The Magician	Skilled developer, elegant solution	Over-engineering, unnecessary complexity	Code quality vs. complexity ratio
II The High Priestess	Deep domain knowledge, institutional memory	Hidden knowledge, undocumented decisions	Documentation coverage
III The Empress	Productive growth, feature velocity	Bloat, feature creep, scope expansion	Lines added per sprint
IV The Emperor	Strong architecture, clear structure	Rigid, resistant to change	Coupling metrics
V The Hierophant	Following conventions, best practices	Dogmatic, cargo cult code	Convention adherence
VI The Lovers	Good integration, harmony between modules	Merge conflicts, incompatible changes	Branch conflict rate
VII The Chariot	Fast progress, shipping frequently	Moving too fast, breaking things	Deploy frequency vs. failure rate
VIII Strength	Resilient system, good error handling	Brittle, fragile under load	Error rate trends
IX The Hermit	Focused deep work, quality code	Isolated silos, no collaboration	Contributor diversity
X Wheel of Fortune	Change coming, transition period	Chaotic changes, instability	Commit velocity variance
XI Justice	Fair code review, balanced workload	Unbalanced team load, review bottleneck	PR review distribution
XII The Hanged Man	Deliberate pause, waiting for clarity	Stuck, blocked, stalled PRs	Open PR age
XIII Death	Transformation, old code removed	Resistance to change, zombie code	Code deletion rate
XIV Temperance	Balanced approach, moderate pace	Extremes, feast-or-famine development	Commit frequency variance
XV The Devil	Technical debt, dependency on bad patterns	Breaking free, refactoring debt away	Tech debt trend
XVI The Tower	Major rewrite, breaking change	Catastrophic failure, production incident	Major refactors, incidents
XVII The Star	Hope, improving trends, clear path	Lost direction, declining metrics	Positive metric trends
XVIII The Moon	Unclear requirements, ambiguous code	Illumination, bugs revealed by tests	Bug discovery rate
XIX The Sun	Success, high coverage, clean CI	Overconfidence, false sense of security	Coverage + passing tests
XX Judgement	Code review, retrospective, accountability	Blame, post-mortem finger-pointing	Review quality
XXI The World	Shipped, complete, production success	Unfinished, perpetual beta	Release completion

The Daily Horoscope

text

╔══════════════════════════════════════════════════════════════╗
║           ⭐ DAILY CODE HOROSCOPE — March 3, 2026 ⭐         ║
╠══════════════════════════════════════════════════════════════╣
║                                                              ║
║  Your sign: ♒ Aquarius (based on project birth date)        ║
║                                                              ║
║  Today's celestial alignment favors refactoring. Mercury     ║
║  is in retrograde in your dependency graph — avoid           ║
║  upgrading packages today. Venus aligns with your test       ║
║  suite, making it an excellent day for writing tests.        ║
║                                                              ║
║  The stars warn: a merge conflict brews on the horizon.      ║
║  Two branches approach the same file. Communicate with       ║
║  your fellow developers before the celestial collision.      ║
║                                                              ║
║  Lucky file: src/utils/formatter.ts                          ║
║  Lucky commit message: "refactor: simplify and clarify"     ║
║  Avoid: force-pushing during Mercury retrograde              ║
║                                                              ║
║  REAL DATA BEHIND THE PROPHECY:                              ║
║  ├── 2 branches are modifying shared files (merge risk)      ║
║  ├── 3 dependencies have updates but 1 has breaking changes  ║
║  ├── Test suite has been neglected (last test added: 8 days) ║
║  └── src/utils/ has low complexity (safe to refactor)        ║
║                                                              ║
╚══════════════════════════════════════════════════════════════╝

The Crystal Ball

text

╔══════════════════════════════════════════════════════════════╗
║              🔮 THE CRYSTAL BALL SPEAKS 🔮                   ║
╠══════════════════════════════════════════════════════════════╣
║                                                              ║
║  "I see... I see..."                                         ║
║                                                              ║
║  "A great storm gathers in the Payment Realm.                ║
║   The ancient one (invoice-generator.js) stirs.              ║
║   Its power weakens. A successor must be chosen              ║
║   before the autumn equinox, or chaos shall reign."          ║
║                                                              ║
║  TRANSLATION:                                                ║
║  invoice-generator.js hasn't been maintained in 18 months.   ║
║  It handles $2M/month with 0 tests. Based on dependency      ║
║  deprecation timelines, its core PDF library (pdfkit v0.11)  ║
║  reaches end-of-life in September. If not migrated before    ║
║  then, the invoicing system breaks on the next Node upgrade. ║
║                                                              ║
║  "The crystal ball never lies. It just speaks in metaphor.   ║
║   Because the truth, delivered straight, is too boring for   ║
║   anyone to read." — The Oracle                              ║
║                                                              ║
╚══════════════════════════════════════════════════════════════╝

Fortune Cookies

Quick one-liners for any occasion:

text

🥠 "A dependency you trust will betray you this month."
   (You have 3 packages with known CVEs unpatched.)

🥠 "The bug you seek is not where you are looking."
   (Last 3 bug fixes were in different files than initially suspected.)

🥠 "An old friend returns with unexpected news."
   (A developer who hasn't committed in 90 days just pushed.)

🥠 "Beware the function that promises simplicity."
   (getUser() has a cyclomatic complexity of 34.)

🥠 "Your tests protect you. Tend to them."
   (Coverage dropped 2% this week.)

🥠 "The merge will be smoother than you fear."
   (Feature branch has 0 conflicts with main.)

When to Invoke

• Morning ritual — Check your horoscope before coding (it's metrics in disguise)
• Sprint planning — Draw a three-card reading for the sprint ahead
• Team meetings — More engaging than a Jira dashboard
• When you need a sign — The Crystal Ball sees all (all the metrics you've been ignoring)
• For fun — Fortune cookies at standup

Why It Matters

Metrics are important but boring. Prophecies are fun but meaningless. Code Oracle is both — real data that people actually want to hear, wrapped in a presentation that makes them laugh, share, and (most importantly) act on the information.

Because nobody has ever shared a Grafana dashboard in Slack for fun. But they WILL share a tarot reading that says "The Tower rises in your payments module."

Zero external dependencies. Zero API calls. Pure data-driven divination.