forecast

Analyzes git history to forecast file growth trends and risks.

71|7|Updated Apr 4, 2026

Search Tags:#forecast #git-history #trend-analysis #risk-prediction #code-complexity #timewarp

Ready to run

npx skills add https://github.com/mbwsims/claude-universe --skill forecast-mbwsims

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: forecast
Source: https://github.com/mbwsims/claude-universe/tree/main/skills/forecast
Command: npx skills add https://github.com/mbwsims/claude-universe --skill forecast-mbwsims

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The forecast skill anticipates files that will become problematic by analyzing growth, churn, and complexity trends, helping teams intervene before issues arise.

Core Features & Use Cases

Trend Detection: Computes acceleration in line count, function count, and churn using timewarp MCP or git history.
Projection: Projects future size and churn to highlight when files will cross critical thresholds.
Actionable Recommendations: Provides specific refactoring guidance and saves results to .timewarp/forecast-<date>.json.
Scope Flexibility: Works on the whole repository or a given directory.

Quick Start

Ask the forecast skill to identify the top files on concerning trajectories for the entire project.

Frequently Asked Questions about forecast

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

FAQPage Schema

How do I forecast code complexity trends in a git repository?▼

Code hotspot prediction analyzes git history to compute churn, size, and complexity acceleration, identifying files on concerning growth trajectories before they become critical. It projects future size and churn to highlight when files cross critical thresholds.

How do I predict which files will become code hotspots before they get too complex?▼

Predict emerging code hotspots by analyzing churn and complexity acceleration across the repository. The forecast computes growth trajectories and projects when files will cross critical thresholds, providing actionable refactoring guidance.

Can I run trend analysis on a specific directory instead of the whole repository?▼

Yes, trend analysis supports scope flexibility. You can analyze the whole repository or a specified directory to compute churn, size, and complexity trends, then generate a forecast report with growth patterns and projections.

Do I need timewarp data to analyze git history for growth patterns?▼

No, you do not need timewarp data. The forecast skill computes churn, size, and complexity trends using standard git history, though it also supports timewarp data for the same analysis.

What is the best way to identify files with high churn acceleration in git history?▼

The best way to identify high churn acceleration is to compute churn trends using git history. The forecast skill analyzes these growth patterns to project future size and churn, highlighting files approaching critical thresholds.

How are forecast report results saved and exported?▼

Forecast report results are saved automatically to `.timewarp/forecast-<date>.json`. This file contains the growth patterns, projections, and actionable refactoring recommendations generated from the analysis.