code-oracle_skill

Overview

This skill is a playful codebase analyst that turns real software metrics into tarot-style readings, crystal ball predictions, and daily horoscopes. It surfaces concrete signals — test flakiness, coverage drops, outdated dependencies, churned files — and presents them as memorable prophecies to prompt action. The aim is to make metrics shareable, engaging, and actionable for developer teams.

How this skill works

The skill scans repository metadata, git history, test and CI indicators, dependency status, and simple code metrics (complexity, churn, coverage). It maps quantified trends to a deck of archetypal “cards” and generates three-card readings, horoscopes, crystal-ball alerts, and fortune cookies. Every mystical line is anchored to specific data points and remediation suggestions so teams can move from amusement to fixes.

When to use it

• Daily standups or morning rituals to surface priorities in a fun way
• Sprint planning to highlight technical risks and refactor candidates
• Release readiness checks to detect risky dependencies or flaky tests
• Post-incident reviews to summarize root causes in an accessible format
• As a lightweight engagement tool to improve team awareness of metrics

Best practices

• Treat prophecies as prompts, not absolutes — follow the linked data to validate next steps
• Run readings regularly (daily or per sprint) so trends are visible rather than one-off noise
• Use readings to prioritize small, high-impact fixes (flaky tests, TODOs, out-of-date libs)
• Share short prophecies in team channels to spark discussion and assign action owners
• Combine with CI metrics and codeowners to route findings to the right people

Example use cases

• Morning horoscope shows increased test flakiness; dedicate today’s pairing session to stabilizing CI
• Three-card tarot flags a recent major rewrite with TODOs; schedule a technical debt sprint for affected modules
• Crystal ball warns a core dependency will reach end-of-life; plan a migration before the next runtime upgrade
• Fortune cookie reveals a high-complexity function; add tests and consider extraction to reduce risk
• Sprint planning reading surfaces merge conflict risk between two active branches; improve coordination and code review focus