Track file change history across git commits and summarize evolution.
npx skills add https://github.com/supertyrelle/pelley --skill evolution-supertyrelle
Please help me install this Agent Skill. Skill: evolution Source: https://github.com/supertyrelle/pelley/tree/main/skills/evolution Command: npx skills add https://github.com/supertyrelle/pelley --skill evolution-supertyrelle
It helps you understand how a definition file changed over time, why it looks the way it does, and whether it is stable enough to modify safely.
Ask the evolution skill to analyze skills/evolution/SKILL.md and report its history, stability, and any fix-after-feat patterns.
High-intent search queries and answers about installing and using this skill.
To track a file's git history and assess change stability, this Skill analyzes git log commits to report creation dates, last modifications, edit frequency, and line deltas. It summarizes trends to show whether a file is stable or experiencing rapid churn.
Yes, you can detect rushed fix-after-feat sequences in git commit history. The Skill applies deterministic heuristics to git log data to identify these patterns, helping you investigate quality issues before refactoring definition files.
Git churn analysis measures how frequently a file changes over time. You need it for definition files like skills, agents, and rules to understand recent growth or shrinkage, evaluate stability, and decide if a file is safe to modify.
Yes, the evolution skill works with optional git commit ranges for timeline analysis. It uses git log history and deterministic heuristics within those ranges to report edit frequency, line deltas, and overall trend for the target file.
The best way to see how a definition file evolved is to analyze its git log history. This Skill tracks total churn, edit frequency, and fix-after-feat patterns, summarizing recent stability to help you review quality before refactoring.
Limitations of using git log heuristics for file stability include relying on deterministic rules rather than semantic context. It reports line deltas and edit frequency accurately, but cannot assess the logical correctness of the changes made.
gufrancoAnalyze uncommitted Git changes and generate conventional commit messages.
HaaaiawdAnalyze Git commit history to detect temporal coupling and code hotspots.
jorgealvesAggregate complexity, test coverage gaps, and change frequency to identify high-risk code hotspots.
RyoMurakami1983Read Git commit history with graph and decoration for learning.
