skills.rest
ronniegeraghty
ronniegeraghtyCOMMUNITY
Explore all skills by this author →
GitHub

embedded-asset-freshness

Validate that site/dist is up to date before code merges.

3|5|Updated Mar 19, 2026
Search Tags:#build#freshness#ci#bundle#site#goembed
One-click install
npx skills add https://github.com/ronniegeraghty/hyoka --skill embedded-asset-freshness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: embedded-asset-freshness
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.squad/skills/embedded-asset-freshness
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill embedded-asset-freshness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that the local site/dist bundle is current and committed before merging changes, preventing stale assets from entering PRs and deployments.

Core Features & Use Cases

  • CI-enforced freshness checks compare the committed site/dist with the built output.
  • Provides a clear refresh workflow to rebuild the bundle (e.g., cd site && npm run build) and commit site/dist before PRs are merged.
  • Helps during PR reviews and CI runs diagnose and fix bundle staleness quickly.

Quick Start

Run the repository's CI to ensure site/dist is up to date before merging changes.

Frequently Asked Questions about embedded-asset-freshness

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

FAQPage Schema
How do I check if my site/dist bundle is up to date before a pull request?▼

To check site/dist bundle freshness before a pull request, run CI pipelines to compare the committed bundle with the built output, ensuring deployed assets match committed sources and preventing stale assets from entering merges.

What is a deterministic embed for site bundles and why does CI enforce it?▼

A deterministic embed requires site/dist to be committed and verified by CI workflows, ensuring the embedded bundle exactly matches committed sources before code merges proceed without staleness.

How do I rebuild and commit the site/dist bundle to fix CI freshness failures?▼

To fix CI freshness failures, refresh the bundle by running the build command like cd site && npm run build, then commit site/dist before merging the pull request to align deployed assets.

Does this bundle freshness check require any external dependencies or components?▼

No, the bundle freshness check requires no external dependencies or components, operating directly on committed site/dist output within CI pipelines to validate source matches during pull requests.

Why does my CI pipeline fail when site/dist is not committed?▼

CI pipelines fail when site/dist is not committed because freshness checks compare the committed bundle against built output, rejecting stale assets to enforce deterministic embeds before merges proceed.

Related Skills

Explore More Software Engineering Skills→
Adelie-SquadAdelie-Squad
17

build-test

Run npx tsc --noEmit and npm run build, then verify dist/bin/solo-agents.js exists.

Official
Intermediate
cookeyholdercookeyholder

squash-pr

Squash and merge a GitHub pull request into main after validating review feedback.

Community
Advanced
DaFumDaFum
1

perf-budget-enforcer

Enforce performance budgets for bundle size, load time, and FPS in CI builds.

Community
Intermediate
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced