Analyzes code churn patterns to identify unstable areas that predict defects.
From omen-reportingnpx claudepluginhub panbanda/omen --plugin omen-reportingFetches up-to-date library and framework documentation from Context7 for questions on APIs, usage, and code examples (e.g., React, Next.js, Prisma). Returns concise summaries.
Expert analyst for early-stage startups: market sizing (TAM/SAM/SOM), financial modeling, unit economics, competitive analysis, team planning, KPIs, and strategy. Delegate proactively for business planning queries.
Business analyst specializing in process analysis, stakeholder requirements gathering, gap identification, improvement opportunities, and actionable recommendations for operational efficiency and business value.
Analyze churn data to find instability patterns.
Relative churn: It's not how much code changed, but what percentage of the file changed. High relative churn = strong defect predictor.
Concentration: If top 10 files account for 80% of changes, that's where bugs will appear.
Sustained churn: Files changing every week for months = something is wrong with the design.
For files with sustained or unusual churn:
git log --oneline -- <file_path> to see commit history for the fileThis context helps prioritize which churn is concerning vs expected.