version-drift-check

Detects mismatches between deployed Google Apps Script endpoints and git HEAD source versions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/blucsigma05/tbm-apps-script --skill version-drift-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-drift-check
Source: https://github.com/blucsigma05/tbm-apps-script/tree/main/.claude/scheduled-tasks/version-drift-check
Command: npx skills add https://github.com/blucsigma05/tbm-apps-script --skill version-drift-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents your Google Apps Script deployments from silently drifting out of sync with the git source, so you don’t waste time troubleshooting unexpected behavior caused by forgotten deploys or missing commits.

Core Features & Use Cases

  • Deployed vs. git source comparison: Fetches the deployed version map from the live web endpoint and compares it to the version numbers in your .gs files at git HEAD.
  • Targeted per-file drift reporting: Flags only the files whose deployed version value differs from the version returned by the corresponding get<Name>Version() function in source.
  • Action-oriented priority thresholds: Assigns escalation levels based on how many files are drifting (including direction tagging like deployed > head vs deployed < head).

Quick Start

Ask the AI to run the version-drift-check by comparing the JSON from https://thompsonfams.com/pulse?action=version against the version returns in each .gs file’s get<Name>Version() in C:\Dev\tbm-apps-script HEAD, then report any mismatches with drift direction and priority.

Frequently Asked Questions about version-drift-check

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

FAQPage Schema
How do I detect version drift between my Google Apps Script deployment and git HEAD?

To detect version drift, compare the deployed version JSON from your live GAS web endpoint against the version return values parsed from your `.gs` files at git HEAD. This directly flags any files where the deployed version differs from the source code.

What is Google Apps Script version drift and how does it affect release hygiene?

Google Apps Script version drift occurs when live deployments fall out of sync with git source commits. It breaks release hygiene by causing unexpected behavior from forgotten deploys or missing commits, which this drift check prevents by comparing deployed and head versions.

How do I compare a deployed JSON version map against source code return values?

You compare a deployed JSON version map by fetching it from your `/pulse?action=version` endpoint and parsing each `.gs` file for `get<Name>Version()` return values. The process emits drift counts and direction-aware priority tiers for any mismatches.

Do I need a specific endpoint structure to check for undeployed GAS changes?

Yes, you need a deployed web endpoint that returns per-file version JSON, such as `/pulse?action=version`. The drift check requires this deployed version map to compare against your `.gs` files exposing version functions at git HEAD.

What is the best way to prioritize uncommitted Google Apps Script changes?

The best way to prioritize uncommitted changes is to assign escalation levels based on drift direction and count. This check tags whether deployed versions are greater or less than head versions, creating action-oriented priority thresholds.