skills.rest
tyevans
tyevansCOMMUNITY
Explore all skills by this author →
GitHub

evolution

Analyze a file's commit timeline, line churn, and fix-after-feat cycles using git log.

14|6|Updated Feb 3, 2026
Search Tags:#git#refactoring#stability#history#churn#code evolution
One-click install
npx skills add https://github.com/tyevans/tackline --skill evolution-tyevans
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: evolution
Source: https://github.com/tyevans/tackline/tree/main/skills/workflows/evolution
Command: npx skills add https://github.com/tyevans/tackline --skill evolution-tyevans

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill helps you understand the history and stability of a specific file (like a skill, agent, or rule definition) within a codebase, revealing its development lifecycle and potential design issues.

Core Features & Use Cases

  • Edit History Analysis: Shows commit history, including dates, messages, and line changes.
  • Stability Assessment: Identifies how recently a file was modified and its overall edit frequency.
  • Pattern Detection: Detects "fix-after-feat" cycles, indicating rushed development.
  • Use Case: Before refactoring a critical skill, use this to gauge its stability and understand past changes, ensuring you don't introduce regressions.

Quick Start

Analyze the evolution of the 'skills/workflows/evolution/SKILL.md' file.

Frequently Asked Questions about evolution

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

FAQPage Schema
How do I track git file history to assess code stability before refactoring?â–¼

Track git file history by analyzing commit timelines and line churn to assess code stability. This reveals development patterns like fix-after-feat cycles, helping you avoid introducing regressions during refactoring.

What is a fix-after-feat cycle in version control history?â–¼

A fix-after-feat cycle in version control history is a development pattern where bug fix commits immediately follow feature commits. Detecting this rushed development pattern helps identify potential design issues or instability in a file.

How do I check the edit frequency and churn of a specific file in git?â–¼

Check file edit frequency and churn by parsing git log and git log --stat data. This extracts commit dates, messages, and line changes to evaluate how recently a file was modified and its overall stability.

Does this code evolution analysis work with any git repository?â–¼

Yes, this code evolution analysis works with any git repository. It requires the git dependency to query version control history and analyze the commit timeline and line churn of a specified file.

What's the best way to identify unstable files with high commit churn?â–¼

The best way to identify unstable files with high commit churn is to analyze version control history for edit frequency and development patterns. Assessing commit timelines and line modifications reveals files that may require extra caution during refactoring.

Related Skills

Explore More Software Engineering Skills→
missdeermissdeer

commit

Create local git commits with conventional commit message formatting.

Community
Intermediate
supertyrellesupertyrelle

evolution

Track file change history across git commits and summarize evolution.

Community
Intermediate
amanhsnamanhsn

code-reviewer

Analyze pull requests for complexity, risk, and code quality issues.

Community
Advanced
ClyptAIClyptAI

zoom-out

Map codebase modules and their callers at a high level.

Official
Basic