trend-tracker

Trend Tracker

CRITICAL SEQUENCING REQUIREMENT: This skill MUST run AFTER report-generator has written memory/{site}/latest.md. It reads that file and patches it in-place. If it runs before report-generator completes, latest.md will be incomplete or absent and patching will fail.

You classify findings from the current diagnostic scan as [NEW] or [RECURRING] by comparing against the prior scan stored in memory/{site}/trends.json. You patch inline badges onto finding headings in latest.md, append a resolved-findings summary, and write the updated trends.json with a 2-slot rotation (current becomes prior on the next scan).

Overview

After each diagnostic scan, users want to know whether issues are new or have persisted since the last scan. This skill:

1. Reads the prior scan's findings from trends.json (if it exists)
2. Classifies each current finding as NEW or RECURRING using exact ID match with a fuzzy (finding_type + file_path) fallback
3. Patches inline [NEW] or [RECURRING] badges onto finding headings in latest.md
4. Appends a "Resolved Since Last Scan" section listing findings that disappeared
5. Appends a staleness warning if the prior scan is 90+ days old
6. Writes the updated trends.json with 2-slot rotation (prior_scan = old current_scan, current_scan = this scan)

What this skill does NOT do:

• Connect to the WordPress site via SSH, Docker, or direct access
• Run WP-CLI commands (no wp commands)
• Execute grep or find on the codebase
• Generate new findings through code analysis
• Run any diagnostic checks

What this skill DOES do:

• Read COMBINED_FINDINGS (JSON array passed by /diagnose)
• Read memory/{site}/trends.json for prior scan data (if exists)
• Patch memory/{site}/latest.md with inline trend badges
• Write updated memory/{site}/trends.json

First scan behavior: On first scan, no badges are patched (clean report), and trends.json is written with prior_scan: null. This ensures the first report is uncluttered and the trend data store is initialized correctly.