refresh-ai-journey-stats

Regenerate ai-journey-stats metrics from local session history and publish via git push.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mbriggsy/ai-learning-journey --skill refresh-ai-journey-stats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refresh-ai-journey-stats
Source: https://github.com/mbriggsy/ai-learning-journey/tree/main/projects/ai-journey-stats/.claude/skills/refresh-ai-journey-stats
Command: npx skills add https://github.com/mbriggsy/ai-learning-journey --skill refresh-ai-journey-stats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill regenerates and publishes the ai-journey-stats numbers from local session history, ensuring the live showcase reflects recent work without relying on flaky remote data.

Core Features & Use Cases

  • Build and refresh project metrics from local session data.
  • Validate that the generated stats.json contains meaningful, non-null metrics before publishing.
  • Commit the delta (stats.json + assets) and push to trigger Vercel deployment.

Quick Start

Run this skill to regenerate the ai-journey-stats numbers from local session history and publish the updated stats to the live site.

Frequently Asked Questions about refresh-ai-journey-stats

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

FAQPage Schema
How do I regenerate local project metrics from session history and publish them?

To regenerate local project metrics from session history, you run a local deterministic workflow that rebuilds stats, validates non-empty outputs, and commits the delta via git to trigger deployment.

How does a git-pushed delta deploy updated stats to a live site?

A git-pushed delta deploys updated stats by committing the validated stats.json and assets to git, where pushing the changes triggers an automated deployment pipeline like Vercel to update the live site.

Why does my local stats build fail validation before publishing?

Local stats build validation fails before publishing if the workflow detects empty or null metrics in the generated stats.json, enforcing a safe commit sequence by blocking incomplete data from being pushed to deployment.

Can I use local session data to refresh project metrics without relying on remote APIs?

Yes, you can refresh project metrics using local session data to rebuild numbers deterministically, bypassing flaky remote data sources to ensure the showcase accurately reflects recent work without external dependencies.

What is the safest commit sequence for publishing regenerated stats via git?

The safest commit sequence for publishing regenerated stats involves validating that the generated stats.json contains meaningful non-null metrics first, then committing the delta and pushing to trigger deployment.