skills.rest
mbwsims
mbwsimsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dissect

Trace git history to identify when and why file or function complexity was introduced.

71|7|Updated Apr 4, 2026
Search Tags:#git#refactoring#bisect#code-evolution#timewarp#complexity-archaeology#structural-commits
One-click install
npx skills add https://github.com/mbwsims/claude-universe --skill dissect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dissect
Source: https://github.com/mbwsims/claude-universe/tree/main/skills/dissect
Command: npx skills add https://github.com/mbwsims/claude-universe --skill dissect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Dissect identifies when and why a file or function grew in complexity so teams can make informed refactoring decisions and avoid removing load-bearing code by mistake.

Core Features & Use Cases

  • History-driven complexity analysis: Bisect a file or function through git history to locate structural commits that increased complexity.
  • Structural commit filtering: Focuses on meaningful changes (new functions, added branches, API changes) and ignores cosmetic edits.
  • Timeline and remediation guidance: Produces an evolution timeline with complexity impact, justification from commit context, and concrete refactoring opportunities.
  • Use case: Audit a large source file before a refactor to find vestigial compatibility code, layered workarounds, or concentrated complexity that should be extracted.

Quick Start

Run the dissect skill against src/path/to/file.ext to generate a timeline of structural commits, complexity impact, and refactoring recommendations.

Frequently Asked Questions about dissect

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

FAQPage Schema
How do I trace when code complexity was introduced in a git repository?▼

To trace code complexity in a git repository, bisect file history using git log and git show. This identifies structural commits that introduced complexity, filtering out cosmetic edits to reveal when and why the code evolved.

What is git bisect for code archaeology and when should I use it?▼

Git bisect for code archaeology is a technique to locate historical commits that increased source file complexity. Use it before refactoring to identify vestigial compatibility code, layered workarounds, or concentrated complexity that needs extraction.

How do I audit a source file before refactoring to avoid removing load-bearing code?▼

Audit a source file before refactoring by generating an evolution timeline of structural commits. This highlights complexity impacts and commit context, preventing the accidental removal of load-bearing code by distinguishing meaningful structural changes from cosmetic edits.

Does complexity archaeology work on any git-backed codebase or are there prerequisites?▼

Complexity archaeology works on any git-backed codebase with accessible git history. It reads current files and bisects history using git log, requiring no special dependencies, though MCP timewarp trends can enhance the analysis if available.

What is the best way to find structural commits that increased code complexity?▼

The best way to find structural commits that increased code complexity is to filter git history for meaningful changes like new functions, added branches, or API changes. This ignores cosmetic edits and focuses solely on complexity growth.

Can I get refactoring guidance based on git history and code evolution?▼

Yes, you can get refactoring guidance based on git history by analyzing a file's evolution timeline. This identifies concentrated complexity and vestigial code, outputting concrete refactoring opportunities and complexity impact justifications from commit context.

Related Skills

Explore More Software Engineering Skills→
refactory-langrefactory-lang

speckit-workflows.baseline

Generate baseline-spec.md and current-state.md from codebase and git history.

Official
Advanced
PatkikPatkik

laravel:complexity-guardrails

Reduce cyclomatic complexity in Laravel code with guard clauses and helper extraction.

Community
Intermediate
mbwsimsmbwsims
71

forecast

Analyzes git history to forecast file growth trends and risks.

Community
Intermediate
LilwenzLilwenz

python-refactor

Refactor complex Python code into maintainable implementations with validation.

Community
Advanced