[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79RNKDBMF6Y0DNFGHTYRMG5":3,"skill-same:01M79RNKDBMF6Y0DNFGHTYRMG5":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79RNKDBMF6Y0DNFGHTYRMG5","git-archaeology",null,"Investigate how code reached its current state — when a line, function, import, or whole file was changed or deleted, who removed it, and what it looked like before. Use when `git blame` came up empty, when content has been refactored away, or when you need the full evolution of a function across commits.","alexhawat\u002FmergeCraft","alexhawat","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1254687?v=4","01M79RKRMA3JJ8JZFXZ1YBDT0D","Alex Hawat","01M79RKRNE7VHRR1W30AGW74C2",12,"MIT","https:\u002F\u002Fgithub.com\u002Falexhawat\u002FmergeCraft\u002Fblob\u002Fmain\u002Fsrc\u002Fmergecraft\u002Fskills\u002Fgit-archaeology\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: git-archaeology\ndescription: Investigate how code reached its current state — when a line, function, import, or whole file was changed or deleted, who removed it, and what it looked like before. Use when `git blame` came up empty, when content has been refactored away, or when you need the full evolution of a function across commits.\n---\n\n# Git history archaeology\n\n`git blame` only sees what's still in the working tree. For anything that was\ndeleted, moved, or refactored away, you need the commands below. Most agents\nunder-use them and end up scrolling through `git log -p` instead.\n\n## Output discipline (read first)\n\n`git log -p` on a long-lived file can dump tens of thousands of lines and blow\nthe context window. Always:\n\n1. **Start narrow.** Use `--oneline` or `--stat` to get a list of candidate\n   commits.\n2. **Drill in.** Use `git show \u003Csha> -- \u003Cpath>` for the diff of one specific\n   commit.\n3. **Scope the search.** Add `--since=\"3 months ago\"`, `-n 20`, or a path\n   restriction (`-- \u003Cpath>`) so output stays manageable.\n4. **Avoid `git log -p` without a path filter** on any non-trivial repo.\n\n## Decision tree (by agent intent)\n\n### \"When did this exact line, string, or import disappear?\"\n\n```bash\ngit log -S'\u003Cexact-string>' --oneline -- \u003Cfile>\n```\n\nThe pickaxe. Returns commits that **changed the count** of that string in the\nfile. The most recent hit is typically the removal commit. Add `-p` only after\nyou've narrowed to a few candidates.\n\nNotes:\n- `-S` is exact-string by default. Add `--pickaxe-regex` to make it a regex.\n- The argument is \"cuddled\" with `-S` (`-S'foo bar'`), no space.\n- `-S` will not detect pure in-file moves (count unchanged). Use `-G` for that.\n- `--pickaxe-all` shows the entire changeset of matching commits, useful when\n  a commit changes both a definition and its call sites in other files.\n\n### \"When did the diff stop matching this regex?\"\n\n```bash\ngit log -G'\u003Cregex>' --oneline -- \u003Cfile>\n```\n\nLike `-S` but matches any added or removed hunk line against the regex. Use\n`-G` when:\n- You don't know the exact string but know a pattern.\n- You want to catch in-file moves (`-S` won't).\n- You want to find any diff that touched a pattern, even if the count was\n  preserved (e.g., a refactor that changed call sites without removing the\n  function).\n\n### \"How did this function evolve over time?\"\n\n```bash\ngit log -L :\u003Cfunction-name>:\u003Cfile>\n```\n\nEvery commit that touched the function, with diffs scoped to just the function\nbody. Works for languages git understands (most mainstream ones).\n\n### \"How did lines N–M evolve?\"\n\n```bash\ngit log -L \u003CN>,\u003CM>:\u003Cfile>\n```\n\n### \"What's the full history of this file, including across renames?\"\n\n```bash\ngit log --follow --oneline -- \u003Cfile>      # overview\ngit log --follow -p -- \u003Cfile>             # with diffs (use sparingly)\n```\n\n`--follow` only works for a single file, not directories.\n\n### \"Where was a now-deleted line last present?\"\n\nTwo-step pattern when you have an exact deleted string:\n\n```bash\n# 1. find a historical commit that contained the string\ngit log -S'\u003Cdeleted-string>' --oneline --all -- \u003Cfile>\n\n# 2. reverse-blame from that commit to find the last commit it survived in\ngit blame --reverse \u003Cold-sha>..HEAD -- \u003Cfile>\n```\n\nThe reverse blame tells you, for each line, the last commit it survived in\nbefore being modified or deleted. Pinpoints the exact deletion commit.\n\n### \"This file no longer exists — when was it deleted, and what was in it?\"\n\n```bash\n# find all commits that touched the path, even on other branches\ngit log --all --full-history --oneline -- \u003Cdeleted-path>\n\n# the most recent of those is usually the deletion. confirm:\ngit show \u003Csha> --stat\n\n# view the file's contents at any commit where it existed\ngit show \u003Csha>^:\u003Cdeleted-path>\n```\n\nIf you don't know the path, find it from filename alone:\n\n```bash\n# list all delete events with paths\ngit log --all --diff-filter=D --summary | grep -i '\u003Cfilename>'\n\n# or glob across all branches\ngit log --all --oneline -- '**\u002F\u003Cfilename>.*'\n```\n\n### \"Who deleted it, in one shot?\"\n\n```bash\ngit rev-list -n 1 HEAD -- \u003Cdeleted-path>     # the deletion commit\ngit show $(git rev-list -n 1 HEAD -- \u003Cdeleted-path>) -- \u003Cdeleted-path>\n```\n\n### \"Restore a deleted file (locally, no commit)\"\n\n```bash\ngit restore --source=\u003Cdeletion-sha>^ -- \u003Cdeleted-path>\n# or, on older git:\ngit checkout \u003Cdeletion-sha>^ -- \u003Cdeleted-path>\n```\n\nThe `^` is critical — at the deletion commit the file is already gone, so we\nread from its parent.\n\n### \"Search commit messages, not content\"\n\n```bash\ngit log --all --grep='\u003Ctext>' --oneline\ngit log --all --grep='\u003Ctext>' -i --oneline    # case-insensitive\n```\n\nOrthogonal to `-S`\u002F`-G`, which only see the diff.\n\n## Standard workflow for \"why does this code look like this\"\n\n1. `git log --follow --oneline -- \u003Cfile>` — overview of commits touching it.\n2. If a recent commit looks suspicious: `git show \u003Csha> -- \u003Cfile>`.\n3. If you expected to find something and it's missing:\n   `git log -S'\u003Cexpected-string>' --oneline -- \u003Cfile>`.\n4. For a specific function's full lifecycle:\n   `git log -L :\u003Cfn>:\u003Cfile>`.\n5. For the deletion point of a known string: pickaxe to find an old commit\n   that contained it, then `git blame --reverse \u003Cold-sha>..HEAD -- \u003Cfile>`.\n\n## Useful flags reference\n\n| Flag | Effect |\n|------|--------|\n| `--all` | Search all refs, not just the current branch. Use when investigating something that may have lived only on a feature branch. |\n| `--full-history` | Keeps commits that history-simplification would otherwise drop. Needed for accurate history across merges. |\n| `--follow` | Track a single file across renames. Single-file only. |\n| `-M` \u002F `-C` | Detect renames (`-M`) and copies (`-C`) when reading diffs. |\n| `--diff-filter=D` | Restrict to commits that **deleted** something. `A`=added, `M`=modified, `R`=renamed. |\n| `--source` | When combined with `--all`, annotate each commit with the ref it was reached from. |\n| `--pickaxe-all` | With `-S`\u002F`-G`, show all files in the matching commit, not just the matching file. |\n| `--pickaxe-regex` | Treat the `-S` argument as a regex. |\n| `--since` \u002F `--until` | Time-bound the search. Cheap perf win on big repos. |\n| `-n \u003Ccount>` | Cap result count. |\n| `--stat` | Per-commit file stats instead of full patches. Good first pass. |\n\n## Notes and pitfalls\n\n- Always include `--` before paths to disambiguate from refs (e.g.\n  `git log -S'foo' -- src\u002Fauth.ts`).\n- `-S` triggers on **count change**. A pure refactor that moves a line within\n  the same file will not match. Use `-G` for those.\n- `-G` runs diff twice and greps; it's slower than `-S`. Scope with paths and\n  `--since` on big repos.\n- Without `--all`, `git log -- \u003Cpath>` shows nothing if the path never existed\n  on the current branch. When in doubt, add `--all`.\n- `git log --full-history -- \u003Cpath>` alone has had bugs in some git versions\n  for deleted files; pair with `--all` for reliability.\n- For files that were renamed, `git log -- \u003Cnew-path>` only shows post-rename\n  history. Use `--follow` (one file) or `git log --all -- \u003Cold-path>` when\n  hunting across rename events.\n","# Git history archaeology\n\n`git blame` only sees what's still in the working tree. For anything that was\ndeleted, moved, or refactored away, you need the commands below. Most agents\nunder-use them and end up scrolling through `git log -p` instead.\n\n## Output discipline (read first)\n\n`git log -p` on a long-lived file can dump tens of thousands of lines and blow\nthe context window. Always:\n\n1. **Start narrow.** Use `--oneline` or `--stat` to get a list of candidate\n   commits.\n2. **Drill in.** Use `git show \u003Csha> -- \u003Cpath>` for the diff of one specific\n   commit.\n3. **Scope the search.** Add `--since=\"3 months ago\"`, `-n 20`, or a path\n   restriction (`-- \u003Cpath>`) so output stays manageable.\n4. **Avoid `git log -p` without a path filter** on any non-trivial repo.\n\n## Decision tree (by agent intent)\n\n### \"When did this exact line, string, or import disappear?\"\n\n```bash\ngit log -S'\u003Cexact-string>' --oneline -- \u003Cfile>\n```\n\nThe pickaxe. Returns commits that **changed the count** of that string in the\nfile. The most recent hit is typically the removal commit. Add `-p` only after\nyou've narrowed to a few candidates.\n\nNotes:\n- `-S` is exact-string by default. Add `--pickaxe-regex` to make it a regex.\n- The argument is \"cuddled\" with `-S` (`-S'foo bar'`), no space.\n- `-S` will not detect pure in-file moves (count unchanged). Use `-G` for that.\n- `--pickaxe-all` shows the entire changeset of matching commits, useful when\n  a commit changes both a definition and its call sites in other files.\n\n### \"When did the diff stop matching this regex?\"\n\n```bash\ngit log -G'\u003Cregex>' --oneline -- \u003Cfile>\n```\n\nLike `-S` but matches any added or removed hunk line against the regex. Use\n`-G` when:\n- You don't know the exact string but know a pattern.\n- You want to catch in-file moves (`-S` won't).\n- You want to find any diff that touched a pattern, even if the count was\n  preserved (e.g., a refactor that changed call sites without removing the\n  function).\n\n### \"How did this function evolve over time?\"\n\n```bash\ngit log -L :\u003Cfunction-name>:\u003Cfile>\n```\n\nEvery commit that touched the function, with diffs scoped to just the function\nbody. Works for languages git understands (most mainstream ones).\n\n### \"How did lines N–M evolve?\"\n\n```bash\ngit log -L \u003CN>,\u003CM>:\u003Cfile>\n```\n\n### \"What's the full history of this file, including across renames?\"\n\n```bash\ngit log --follow --oneline -- \u003Cfile>      # overview\ngit log --follow -p -- \u003Cfile>             # with diffs (use sparingly)\n```\n\n`--follow` only works for a single file, not directories.\n\n### \"Where was a now-deleted line last present?\"\n\nTwo-step pattern when you have an exact deleted string:\n\n```bash\n# 1. find a historical commit that contained the string\ngit log -S'\u003Cdeleted-string>' --oneline --all -- \u003Cfile>\n\n# 2. reverse-blame from that commit to find the last commit it survived in\ngit blame --reverse \u003Cold-sha>..HEAD -- \u003Cfile>\n```\n\nThe reverse blame tells you, for each line, the last commit it survived in\nbefore being modified or deleted. Pinpoints the exact deletion commit.\n\n### \"This file no longer exists — when was it deleted, and what was in it?\"\n\n```bash\n# find all commits that touched the path, even on other branches\ngit log --all --full-history --oneline -- \u003Cdeleted-path>\n\n# the most recent of those is usually the deletion. confirm:\ngit show \u003Csha> --stat\n\n# view the file's contents at any commit where it existed\ngit show \u003Csha>^:\u003Cdeleted-path>\n```\n\nIf you don't know the path, find it from filename alone:\n\n```bash\n# list all delete events with paths\ngit log --all --diff-filter=D --summary | grep -i '\u003Cfilename>'\n\n# or glob across all branches\ngit log --all --oneline -- '**\u002F\u003Cfilename>.*'\n```\n\n### \"Who deleted it, in one shot?\"\n\n```bash\ngit rev-list -n 1 HEAD -- \u003Cdeleted-path>     # the deletion commit\ngit show $(git rev-list -n 1 HEAD -- \u003Cdeleted-path>) -- \u003Cdeleted-path>\n```\n\n### \"Restore a deleted file (locally, no commit)\"\n\n```bash\ngit restore --source=\u003Cdeletion-sha>^ -- \u003Cdeleted-path>\n# or, on older git:\ngit checkout \u003Cdeletion-sha>^ -- \u003Cdeleted-path>\n```\n\nThe `^` is critical — at the deletion commit the file is already gone, so we\nread from its parent.\n\n### \"Search commit messages, not content\"\n\n```bash\ngit log --all --grep='\u003Ctext>' --oneline\ngit log --all --grep='\u003Ctext>' -i --oneline    # case-insensitive\n```\n\nOrthogonal to `-S`\u002F`-G`, which only see the diff.\n\n## Standard workflow for \"why does this code look like this\"\n\n1. `git log --follow --oneline -- \u003Cfile>` — overview of commits touching it.\n2. If a recent commit looks suspicious: `git show \u003Csha> -- \u003Cfile>`.\n3. If you expected to find something and it's missing:\n   `git log -S'\u003Cexpected-string>' --oneline -- \u003Cfile>`.\n4. For a specific function's full lifecycle:\n   `git log -L :\u003Cfn>:\u003Cfile>`.\n5. For the deletion point of a known string: pickaxe to find an old commit\n   that contained it, then `git blame --reverse \u003Cold-sha>..HEAD -- \u003Cfile>`.\n\n## Useful flags reference\n\n| Flag | Effect |\n|------|--------|\n| `--all` | Search all refs, not just the current branch. Use when investigating something that may have lived only on a feature branch. |\n| `--full-history` | Keeps commits that history-simplification would otherwise drop. Needed for accurate history across merges. |\n| `--follow` | Track a single file across renames. Single-file only. |\n| `-M` \u002F `-C` | Detect renames (`-M`) and copies (`-C`) when reading diffs. |\n| `--diff-filter=D` | Restrict to commits that **deleted** something. `A`=added, `M`=modified, `R`=renamed. |\n| `--source` | When combined with `--all`, annotate each commit with the ref it was reached from. |\n| `--pickaxe-all` | With `-S`\u002F`-G`, show all files in the matching commit, not just the matching file. |\n| `--pickaxe-regex` | Treat the `-S` argument as a regex. |\n| `--since` \u002F `--until` | Time-bound the search. Cheap perf win on big repos. |\n| `-n \u003Ccount>` | Cap result count. |\n| `--stat` | Per-commit file stats instead of full patches. Good first pass. |\n\n## Notes and pitfalls\n\n- Always include `--` before paths to disambiguate from refs (e.g.\n  `git log -S'foo' -- src\u002Fauth.ts`).\n- `-S` triggers on **count change**. A pure refactor that moves a line within\n  the same file will not match. Use `-G` for those.\n- `-G` runs diff twice and greps; it's slower than `-S`. Scope with paths and\n  `--since` on big repos.\n- Without `--all`, `git log -- \u003Cpath>` shows nothing if the path never existed\n  on the current branch. When in doubt, add `--all`.\n- `git log --full-history -- \u003Cpath>` alone has had bugs in some git versions\n  for deleted files; pair with `--all` for reliability.\n- For files that were renamed, `git log -- \u003Cnew-path>` only shows post-rename\n  history. Use `--follow` (one file) or `git log --all -- \u003Cold-path>` when\n  hunting across rename events.\n",{"name":5,"description":7},"main","c0404bd8c54b33a576f0b66b8740122d7256d321","src\u002Fmergecraft\u002Fskills\u002Fgit-archaeology",5,"https:\u002F\u002Fgithub.com\u002Falexhawat\u002FmergeCraft","https:\u002F\u002Fgithub.com\u002Falexhawat\u002FmergeCraft#-get-started-in-3-steps","https:\u002F\u002Fgithub.com\u002Falexhawat","AI-native engineer in Amsterdam. Building exclusively with agentic AI.","2026-11-15 04:52:32",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add alexhawat\u002FmergeCraft --skill git-archaeology",{"tool":39,"command":40},"bunx","bunx skills add alexhawat\u002FmergeCraft --skill git-archaeology",{"tool":42,"command":43},"pnpm","pnpm dlx skills add alexhawat\u002FmergeCraft --skill git-archaeology","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falexhawat\u002FmergeCraft\u002Fblob\u002Fmain\u002Fsrc\u002Fmergecraft\u002Fskills\u002Fgit-archaeology\u002FSKILL.md",true,[],[48,55,60,65,70,75],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M79RNF1TMQWNAKKV1FA6HCN0","mergecraft","Set up, run, and troubleshoot mergeCraft — the BYOK AI PR review GitHub Action and CLI. Use when the user asks to install or configure mergeCraft, add AI PR review to a repo, run a local review, interpret mergecraft-approval status or findings, configure models in .mergecraft\u002Fconfig.yaml, use mergecraft mcp serve, or debug a failing mergeCraft workflow.","https:\u002F\u002Fgithub.com\u002Falexhawat\u002FmergeCraft\u002Fblob\u002Fmain\u002Fskills\u002Fopencode\u002Fmergecraft\u002FSKILL.md",[],[],{"skillNo":56,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79RN8VQWTKEWT6SMCB2874Q","https:\u002F\u002Fgithub.com\u002Falexhawat\u002FmergeCraft\u002Fblob\u002Fmain\u002Fskills\u002Fopenclaw\u002Fmergecraft\u002FSKILL.md",[],[],{"skillNo":61,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M79RN31H176QC23BJRY6FBVW","https:\u002F\u002Fgithub.com\u002Falexhawat\u002FmergeCraft\u002Fblob\u002Fmain\u002Fskills\u002Fmergecraft\u002FSKILL.md",[],[],{"skillNo":66,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79RMYGSB312HBVMAAF3ZF8H","https:\u002F\u002Fgithub.com\u002Falexhawat\u002FmergeCraft\u002Fblob\u002Fmain\u002Fskills\u002Fhermes\u002Fmergecraft\u002FSKILL.md",[],[],{"skillNo":71,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79RMSR72M4GYR661R7W41WV","https:\u002F\u002Fgithub.com\u002Falexhawat\u002FmergeCraft\u002Fblob\u002Fmain\u002Fskills\u002Fgrok-bot\u002Fmergecraft\u002FSKILL.md",[],[],{"skillNo":76,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79RMN8RXFRSM0RMSS1ZDV8Y","https:\u002F\u002Fgithub.com\u002Falexhawat\u002FmergeCraft\u002Fblob\u002Fmain\u002Fskills\u002Fgemini-cli\u002Fmergecraft\u002FSKILL.md",[],[]]