skills.rest
gitlabhq
gitlabhqOFFICIAL
Explore all skills by this author →
WebsiteGitHub

code-history

Investigate code history, usage, and liveness using Git commands.

34|9|Updated Mar 12, 2026
Search Tags:#code analysis#refactoring#code history#dead code#git blame#git log
One-click install
npx skills add https://github.com/gitlabhq/orbit-knowledge-graph --skill code-history
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-history
Source: https://github.com/gitlabhq/orbit-knowledge-graph/tree/main/.claude/skills/code-history
Command: npx skills add https://github.com/gitlabhq/orbit-knowledge-graph --skill code-history

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps determine if code is dead, understand its origins and evolution, and assess its safety for removal or refactoring.

Core Features & Use Cases

  • Dead Code Detection: Identify code that is no longer used or referenced.
  • Code Provenance: Understand who introduced specific code and why.
  • Refactoring Safety: Assess the impact of removing or modifying code by finding all its callers.
  • Use Case: Before refactoring a large module, use this Skill to find all existing callers and understand the history of the code you plan to change.

Quick Start

Investigate the history and usage of the 'calculate_metrics' function in the 'src/utils.rs' file.

Frequently Asked Questions about code-history

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify dead code in a software repository before refactoring?▼

Identify dead code by searching the software repository for unreferenced artifacts and analyzing Git history. This Skill traces code usage and liveness to assess removal safety before refactoring.

What is the best way to understand code provenance and who introduced specific lines?▼

Understand code provenance by running Git blame and Git log commands on the target files. This Skill automates Git blame analysis to reveal who introduced specific code and why.

How do I find all callers of a function to safely modify a module?▼

Find all callers of a function by executing file system searches across the software repository. This Skill locates existing references to assess the impact of modifying or removing code.

Can I use Git command-line tools to investigate code evolution without accessing a remote repository?▼

Yes, you can investigate code evolution using Git command-line tools with local file system access. This Skill requires Git command-line tools and local file system access for code searching and blame analysis.

Does code history analysis work for finding unused functions in a large codebase?▼

Code history analysis works for finding unused functions by searching the repository for references and checking Git logs. This Skill identifies code that is no longer used or referenced within the repository.

Related Skills

Explore More Software Engineering Skills→
AVIDS2AVIDS2
618

memorix-git-memory

Search and inspect Git commit history to retrieve project memory.

Community
Intermediate
SakshamKandelSakshamKandel

health

Run type checks, linting, tests, and dead-code analysis to produce a 0-10 health score.

Community
Intermediate
GeargrindadminGeargrindadmin

lint-and-validate

Run ESLint, Ruff, MyPy, and npm audit to validate code.

Community
Intermediate
DayoptDayopt

cleanup

Detect and remove unused code, dead imports, and console statements in TypeScript/JavaScript projects.

Official
Advanced