{"id":50977081,"url":"https://github.com/twitu/indiana-codes","last_synced_at":"2026-06-19T09:30:40.701Z","repository":{"id":354357689,"uuid":"1223251000","full_name":"twitu/indiana-codes","owner":"twitu","description":"Read a codebase like a book — chapter-by-chapter git/PR/issue archaeology with interactive Q\u0026A. Adds the /dig slash command for Claude Code.","archived":false,"fork":false,"pushed_at":"2026-04-28T07:20:41.000Z","size":497,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-04-28T09:18:27.414Z","etag":null,"topics":["ai-agents","claude-code","claude-code-plugin","claude-code-skill","codebase","documentation","git-archaeology","onboarding"],"latest_commit_sha":null,"homepage":"https://twitu.github.io/indiana-codes/","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/twitu.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2026-04-28T06:32:14.000Z","updated_at":"2026-04-28T07:20:24.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/twitu/indiana-codes","commit_stats":null,"previous_names":["twitu/indiana-codes"],"tags_count":null,"template":false,"template_full_name":null,"purl":"pkg:github/twitu/indiana-codes","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/twitu%2Findiana-codes","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/twitu%2Findiana-codes/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/twitu%2Findiana-codes/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/twitu%2Findiana-codes/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/twitu","download_url":"https://codeload.github.com/twitu/indiana-codes/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/twitu%2Findiana-codes/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":34526065,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-19T02:00:06.005Z","response_time":61,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ai-agents","claude-code","claude-code-plugin","claude-code-skill","codebase","documentation","git-archaeology","onboarding"],"created_at":"2026-06-19T09:30:39.927Z","updated_at":"2026-06-19T09:30:40.696Z","avatar_url":"https://github.com/twitu.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Code Archaeology\n\n\u003e *Read the codebase like a book. Chapter by chapter. With a guide who answers back.*\n\nA skill for AI coding agents (Claude Code, OpenCode, Cursor, …) that turns a repo's git history + GitHub issues/PRs/discussions into a chapter-based, interactive learning experience. You run `/dig`, the agent does the digging, and you come out the other side understanding the codebase like someone who's been on the team a year.\n\n## You just joined the team\n\nYou open the repo. **2,000 commits.** 200+ tickets. 14 contributors. Half of them don't work here anymore. The README was last updated in 2023.\n\nWhat do you do?\n\n![wing-it](./wing-it.jpg)\n\nYou read the code. You find a decision that makes no sense. You want to ask your teammates but you've been here 3 days and they seem busy and you don't want to be *that* person.\n\nWhat do you do?\n\n![hack right?](./hack-right.jpg)\n\nYou be Indiana Jones \\*cracks whip. You **dig**. You study the history, chapter by chapter, until you understand *why* things are the way they are — and you can challenge them with evidence.\n\n![tame-the-code](./tame-the-code.jpg)\n\n## What it does\n\n1. **Survey** — commits, contributors, ticket patterns, infra files, gaps in documentation, the suspicious silence around `legacy_v2/`.\n2. **Identify chapters** — natural breakpoints in the project's life. Team transitions. Migrations. The Great Refactor of 2022. The incident that shall not be named.\n3. **Deep-dive** — for each chapter, walk you through what happened, who did it, why, and what got abandoned along the way.\n4. **Quiz you back** — *why not the simpler thing?* *what breaks if this assumption is wrong?* *was this eventually replaced?* You answer. You learn. The chapter writes itself into `PROJECT_HISTORY.md` and `chapters/\u003cn\u003e-\u003cname\u003e.md`.\n\nThe Q\u0026A is the load-bearing phase. Steps 1–3 produce a draft; step 4 — the conversation — is where you actually learn the system.\n\n## Install\n\n### Claude Code (one-liner via marketplace)\n\n```\n/plugin marketplace add twitu/indiana-codes\n/plugin install dig@indiana-codes\n```\n\nThat's it. Restart and `/dig` will appear in your slash-command menu in any repo with git history.\n\n### Manual install (OpenCode, Cursor, anything else)\n\nClone the repo first. The skill content is identical across agents — only the install path differs.\n\n```bash\ngit clone https://github.com/twitu/indiana-codes ~/.local/share/indiana-codes\ncd ~/.local/share/indiana-codes\n```\n\n#### OpenCode\n\n```bash\nmkdir -p ~/.config/opencode/skills ~/.config/opencode/commands\nln -sf ~/.local/share/indiana-codes/dig         ~/.config/opencode/skills/dig\nln -sf ~/.local/share/indiana-codes/commands/dig.md  ~/.config/opencode/commands/dig.md\n```\n\n#### Cursor\n\nCursor has no skills directory, so the command file points the agent at the cloned `SKILL.md` directly:\n\n```bash\nmkdir -p ~/.cursor/commands\ncat \u003e ~/.cursor/commands/dig.md \u003c\u003cEOF\n---\ndescription: Code archaeology — chapter-based history walkthrough\n---\nFollow the skill instructions in $HOME/.local/share/indiana-codes/dig/SKILL.md to perform a codebase excavation pass on this repository.\nEOF\n```\n\nProject-scoped install (commits with the repo) is the same, but writes to `.cursor/commands/` instead of `~/.cursor/commands/`.\n\n#### Other agents (Codex, Aider, Continue, Zed, …)\n\nDrop the contents of `dig/SKILL.md` into your agent's long-lived instruction file (`AGENTS.md`, `~/.aider.conf.yml`, system prompt, etc.). See [OTHER_AGENTS.md](./OTHER_AGENTS.md) for per-agent recipes.\n\nRestart your agent. You should see `/dig` when you type `/`.\n\n## Use it\n\nIn your agent of choice, in any repo with git history:\n\n```\n/dig\n```\n\nThe agent surveys the repo, proposes chapters, and asks which one to start with. Then:\n\n```\nTell me about chapter 1.\n```\n\n```\nWhy didn't they just use Postgres here?\n```\n\n```\nWas the v2 API ever finished, or is it abandonware?\n```\n\n```\nSkip ahead to the chapter about the auth migration.\n```\n\nIt answers. You push back. By the end of each chapter, you know the chapter — and a markdown file knows it too.\n\nIn a fresh chat, no need to re-run `/dig` — just point the agent at the existing `PROJECT_HISTORY.md`:\n\n```\nBased on PROJECT_HISTORY.md, walk me through chapter 3.\n```\n\n## See it in action\n\nSample books — the output of running this on well-known repos — live on the [project site](https://twitu.github.io/indiana-codes/). Good place to start if you want a feel for what a finished excavation looks like before you point it at your own repo.\n\n## Connect more sources (optional)\n\nThe skill uses whatever it can find. More sources = better chapters.\n\n| Source | How |\n|---|---|\n| Git history | Built in. Always on. |\n| GitHub issues / PRs / discussions | Local [`gh`](https://cli.github.com/) CLI works out of the box. The official [GitHub MCP](https://github.com/github/github-mcp-server) is even better. |\n| GitHub releases | Same: `gh release` or the MCP. |\n| Jira / Linear / Confluence / Notion | If your team has the corresponding MCP configured in your agent, the skill picks it up automatically — no extra setup. |\n| Local docs | `docs/`, `adr/`, `rfc/`, `CHANGELOG.md` — read automatically. |\n\n## License\n\nMIT. Go dig.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftwitu%2Findiana-codes","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftwitu%2Findiana-codes","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftwitu%2Findiana-codes/lists"}