History
Smart temporal analysis using git history - Hotspots, Coupling, and Recent Contributors
Install
/plugin marketplace add lis186/SourceAtlasThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lis186/SourceAtlas --skill historygit clone --depth 1 https://github.com/lis186/SourceAtlas.git /tmp/SourceAtlas
mkdir -p ~/.claude/skills
cp -r /tmp/SourceAtlas/plugin/commands/history ~/.claude/skills/historyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# SourceAtlas: Smart Temporal Analysis (Git History) > **Constitution**: [ANALYSIS_CONSTITUTION.md](../../../ANALYSIS_CONSTITUTION.md) v1.0 ## Context **Analysis Scope:** $ARGUMENTS (default: entire repository) **Goal:** Extract actionable insights from git history **Time Limit:** 5-10 minutes **Prerequisite:** code-maat (will ask permission to install if missing) ## Quick Start 1. **Check cache** (skip if `--force` flag present) 2. **Check code-maat** installation (install if needed with permission) 3. **Generate git log** (last 12 months, code-maat compatible) 4. **Run analyses**: Hotspots, Coupling, Contributors 5. **Risk assessment** combining all dimensions 6. **Generate report** following [output-template.md](output-template.md) 7. **Verify output** using [verification-guide.md](verification-guide.md) 8. **Auto-save** to `.sourceatlas/history.md` ## Your Task You are analyzing git commit history to understand: 1. **Hotspots** - Files changed most frequently (likely complex/risky) 2. **Temporal Coupling** - Files that change together (hidden dependencies) 3. **Recent Contributors** - Who has knowledge of which areas (bus factor) 4. **Risk Areas** - Aggregate assessment for prioritization ### What You'll Discover | Analysis Type | Insight | Business Value | |---------------|---------|----------------| | **Hotspots** | Complexity indicators | Refactoring priorities, technical debt | | **Coupling** | Hidden dependencies | Architecture review targets |
Details
- Skill name
history- Repository
- lis186/SourceAtlas
- Path
plugin/commands/history/SKILL.md- License
- MIT
- Repo updated
- 22 October 2026
FAQ
What does the History skill do?
Smart temporal analysis using git history - Hotspots, Coupling, and Recent Contributors
How do I install the History skill?
Claude Code plugin: /plugin marketplace add lis186/SourceAtlas. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is History popular?
It lives in lis186/SourceAtlas, which has 49 GitHub stars and 4 forks.
Related skills
Code Flow Tracer
49lis186/SourceAtlas
Trace code execution paths and data flow. Use when user asks "how does X work", "what happens when X", "trace the flow of X", "where does data come from", or needs to understand feature implementation.
Codebase Overview
49lis186/SourceAtlas
Quickly understand a new codebase's architecture, tech stack, and patterns. Use when user asks "what is this project", "project overview", "how is this codebase structured", "what tech stack", or when onboarding to a new codebase.
Dependency Analyzer
49lis186/SourceAtlas
Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.
Ijfw Commit
43FerroxLabs/wayland-core
Terse conventional commits. Trigger: commit, git commit, /ijfw-commit
Uw Unity Project Setup
47devdavv/unity-ai-workflow
Full project initialization wizard from ProjectConfig, including folders, packages, Git, and MCP setup. Use when setting up a new Unity project from scratch, creating the folder structure, or bootstrapping infrastructure. Triggers on requests like "set up a new project", "create folder structure", "initialize the project", or "/uw-cmd-setup-project". Reads ProjectConfig.yaml for all decisions.
Careful Delete
62ElliotJLT/Claude-Skill-Potions
Before any destructive or irreversible operation (rm -rf, DROP TABLE, DELETE, force push, branch deletion, truncate), orchestrate a safety cycle: assess blast radius → confirm explicitly → document what happened. Chains pre-mortem and you-sure with built-in documentation. No dangerous operation executes without ceremony.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.