reflect-trends

Analyze three days of git history and GitHub issues for development health risks.

1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/silenvx/flow-development-program --skill reflect-trends
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect-trends
Source: https://github.com/silenvx/flow-development-program/tree/main/examples/dekita/.claude/skills/reflect-trends
Command: npx skills add https://github.com/silenvx/flow-development-program --skill reflect-trends

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill surfaces hidden development health issues by performing multi-granularity analysis across recent activity, enabling teams to spot risky patterns before they escalate.

Core Features & Use Cases

  • 3-day trend assessment: Measure fix/feat ratios from the repository to spot unhealthy reactive development.
  • NOT_PLANNED Issue detection: Surface closed issues lacking planning context to reduce decision drift.
  • Block-pattern detection: Identify recurring blocking patterns in recent sessions and logs.
  • Use Case: When a project shows a high fix-to-feature ratio and frequent NOT_PLANNED issues, run reflect-trends to surface actionable improvements and guardrails.

Quick Start

Run the reflect-trends analysis commands to generate a health snapshot: git log --oneline --since="3 days ago" | grep -cE "(fix|refactor)[:(]" git log --oneline --since="3 days ago" | grep -cE "feat[:(]" gh issue list --state closed --limit 20 --json number,title,stateReason --jq '.[] | select(.stateReason == "NOT_PLANNED") | "#(.number): (.title[0:40])"' tail -100 .claude/logs/execution/hook-errors.log 2>/dev/null | jq -r '.reason[0:50]' 2>/dev/null | sort | uniq -c | sort -rn | head -5

Frequently Asked Questions about reflect-trends

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

FAQPage Schema
How do I analyze recent git history to detect unhealthy development trends?

Analyze recent git history by inspecting the last three days of commit logs to compute fix/feat ratios. This skill uses standard git history inspection to surface reactive development patterns and identify risk signals before they escalate.

How do I find NOT_PLANNED issues in a GitHub repository?

Find NOT_PLANNED issues by running the GitHub CLI to list recently closed issues and filtering by the stateReason field. This skill surfaces closed issues lacking planning context to reduce decision drift in the development workflow.

What is a fix-to-feature ratio and how does it indicate code health?

A fix-to-feature ratio compares the volume of fix or refactor commits against feature commits over a three-day window. A high fix-to-feature ratio indicates unhealthy reactive development and serves as a risk signal for project stability.

Do I need the GitHub CLI to detect blocking patterns in local logs?

You need the GitHub CLI to retrieve closed issue data, but block-pattern detection also relies on local execution logs. The skill processes local hook error logs to identify recurring blocking patterns in recent sessions.

What's the best way to surface hidden code health issues before they escalate?

The best way to surface hidden code health issues is running multi-granularity trend analysis across recent activity. This skill focuses on three-day windows to track fix/feat ratios, NOT_PLANNED issues, and frequent block patterns for actionable insights.

Why does my trend analysis only cover the last three days of git history?

Trend analysis covers the last three days to focus on immediate recent development activity and surface risky patterns quickly. This short window ensures the computed metrics reflect current workflow health rather than long-term historical averages.