tlamatini-static-version-bumper

Name: tlamatini-static-version-bumper
Availability: InStock
Author: XAIHT

Increment STATIC_VERSION in Tlamatini settings.py to bust asset caches.

14|1|Updated Mar 6, 2026

Search Tags:#frontend #python #cache-busting #settings.py #static-version #tlamatini

Ready to run

npx skills add https://github.com/XAIHT/Tlamatini --skill tlamatini-static-version-bumper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tlamatini-static-version-bumper
Source: https://github.com/XAIHT/Tlamatini/tree/main/Tlamatini/agent/skills_pkg/tlamatini_static_version_bumper
Command: npx skills add https://github.com/XAIHT/Tlamatini --skill tlamatini-static-version-bumper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bump STATIC_VERSION in Tlamatini/settings.py to ensure browsers fetch updated CSS+JS bundles after frontend changes.

Core Features & Use Cases

Increment the STATIC_VERSION value in Tlamatini/tlamatini/settings.py to bust caches.
Return a structured result containing old_version, new_version, and changed.
Handle missing STATIC_VERSION gracefully by signaling no changes.

Quick Start

Read STATIC_VERSION from the settings file, increment to the next value, and save.

Frequently Asked Questions about tlamatini-static-version-bumper

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

FAQPage Schema

How do I auto-refresh frontend assets after updating CSS or JavaScript files?▼

To auto-refresh frontend assets, you need cache-busting by bumping the STATIC_VERSION value in your settings.py file. This forces browsers to re-fetch updated CSS and JS bundles instead of loading stale cached versions.

What's the best way to bust browser cache for static files during deployment?▼

Cache-busting for static files during deployment is best handled by incrementing a STATIC_VERSION variable in your settings file. This updates asset URLs, forcing CDNs and browsers to fetch the latest CSS and JS bundles.

How does incrementing a static version variable handle missing values in settings.py?▼

Incrementing a static version variable handles missing STATIC_VERSION values gracefully by signaling no changes were made. It reads the existing version, increments or rotates semver, and returns old_version, new_version, and changed status.

Why do browsers load old CSS and JS after I update my frontend code?▼

Browsers load old CSS and JS because they cache static assets to improve performance. Without cache-busting, such as updating a STATIC_VERSION in settings.py, browsers continue serving stale bundles instead of re-fetching your updated frontend code.

Does cache-busting work for both local development and CDN deployment workflows?▼

Cache-busting works for both local development and CDN deployment workflows by updating STATIC_VERSION in settings.py. It ensures browsers and CDNs re-fetch updated CSS and JS bundles whenever frontend changes occur.