菜单
Traces code history via git blame and log to explain why code exists in its current form. Use when asked about code history, reasoning behind changes, or "when/why did this change".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Commit changes with smart messages. Supports full and partial commits. Use whenever committing changes or handling pre-commit hook failures.
Use the gh CLI for GitHub interactions, plus setup and pushing. Use when interacting with GitHub, setting up GitHub tools, or pushing to remote.
Universal polyglot linting and per-project config management. Use when you need to lint files, understand tool selection logic, invoke linting from commands/agents, or manage mr-sparkle config.
Resolves git merge conflicts by analyzing intent from both sides. Use when merge conflicts are detected or when git operations fail with conflict errors.
Create a pull request with Problem/Solution format. Can optionally commit first. Use when opening PRs or when branch changes are ready for review.
User's README style preferences — ultra-terse, action-focused, <50 lines. Use when writing or reviewing any README file.
| name | code-history |
| description | Traces code history via git blame and log to explain why code exists in its current form. Use when asked about code history, reasoning behind changes, or "when/why did this change". |
Investigate code history and synthesize narrative explanations of why code is the way it is.
Parse the query — determine what to research (file, function, line, concept, pattern)
Research using git archaeology:
--follow to track through renamesgit blame for line-level attributiongit log -S (pickaxe) and git log -G for concept/pattern searchesgh pr list --search "<hash>" --state allSynthesize a narrative, not a list:
Return in this structure:
# Summary
[Direct 2-3 sentence answer to the question]
# Historical Evolution
[Chronological narrative with dates and commit hashes]
# Reasoning
[Why decisions were made — problems, constraints, alternatives considered]
# Supporting Evidence
[Relevant commits quoted, PR discussions, code snippets showing evolution]
# Assessment
[Is this still the right approach? Technical debt? Context changed?]
# Gaps in Historical Record
[What's unclear or missing — only if applicable]
--follow