Name: git-archaeologist
Author: zenodefault

Imported from zenodefault/codesentinel (skills/git-archaeologist/SKILL.md). Install upstream with npx skills add zenodefault/codesentinel --skill git-archaeologist. Copyright stays with the author.

git-archaeologist

Purpose

Reconstruct why a file changed by mining git history, linked ticket IDs, ownership drift, and downstream impact.

Inputs

repoPath: local repository path
filePath: file path inside the repository

Behavior

Run git log --follow for the target file.
Extract commit hash, subject, author email, authored date, and Jira ticket IDs.
Enrich the result with Jira summaries and org-membership checks when credentials are available.
Persist decision history, ghost-author data, and module passports into Durable Memory.

Environment

JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN for ticket enrichment
GITHUB_TOKEN for GitHub org membership lookup
ANTHROPIC_API_KEY for module passport risk summaries

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install git-archaeologist and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zenodefault-codesentinel-git-archaeologist", "kind": "skill", "name": "git-archaeologist", "description": "Reconstruct why a file changed by mining git history, linked ticket IDs, ownership drift, and downstream impact.", "publisher": "zenodefault", "version": "1.0.0", "capabilities": { "domains": [ "coding", "customer_support" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Reconstruct why a file changed by mining git history, linked ticket IDs, ownership drift, and downstream impact." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/zenodefault/codesentinel", "path": "skills/git-archaeologist/SKILL.md", "ref": "de3b2b9217881b06fe98bca11f11df9615753f66", "url": "https://github.com/zenodefault/codesentinel/blob/de3b2b9217881b06fe98bca11f11df9615753f66/skills/git-archaeologist/SKILL.md", "key": "zenodefault/codesentinel/skills/git-archaeologist/SKILL.md" } }, "instructions": "# git-archaeologist\n\n## Purpose\n\nReconstruct why a file changed by mining git history, linked ticket IDs, ownership drift, and downstream impact.\n\n## Inputs\n\n- `repoPath`: local repository path\n- `filePath`: file path inside the repository\n\n## Behavior\n\n1. Run `git log --follow` for the target file.\n2. Extract commit hash, subject, author email, authored date, and Jira ticket IDs.\n3. Enrich the result with Jira summaries and org-membership checks when credentials are available.\n4. Persist decision history, ghost-author data, and module passports into Durable Memory.\n\n## Environment\n\n- `JIRA_BA", "cost": { "context_tokens": 192 } }

git-archaeologist

About