tampermonkey-version

Bump @name and @version headers in Tampermonkey .user.js files before commits.

1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Pepsi1978/proggs --skill tampermonkey-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tampermonkey-version
Source: https://github.com/Pepsi1978/proggs/tree/main/claude-code-setup/commands/tampermonkey-version
Command: npx skills add https://github.com/Pepsi1978/proggs --skill tampermonkey-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically enforces version consistency for Tampermonkey userscripts by bumping header versions before commits.

Core Features & Use Cases

  • Automatic header version bumps for all .user.js files under ~/proggs/Tampermonkey/
  • Ensures both @name and @version lines match after changes
  • Prevents commits when a bump cannot be applied, with clear error reporting

Quick Start

Modify any Tampermonkey .user.js files in ~/proggs/Tampermonkey/ and commit; the skill will automatically bump both the @name and @version headers before the commit.

Frequently Asked Questions about tampermonkey-version

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

FAQPage Schema
How do I automatically bump Tampermonkey userscript versions before a commit?

To automatically bump Tampermonkey userscript versions before a commit, this skill intercepts the commit process and updates the @version header. It ensures @name and @version stay synchronized across all modified .user.js files.

What happens if a Tampermonkey header version bump cannot be applied to a userscript?

If a Tampermonkey header version bump cannot be applied to a userscript, the skill prevents the commit from proceeding. It provides clear error reporting to help you identify and fix the header validation issue before retrying.

Does the automatic header sync work for userscripts outside the main Tampermonkey directory?

No, the automatic header sync only applies to .user.js files located specifically within the ~/proggs/Tampermonkey/ directory. Userscripts stored outside this path will not trigger the pre-commit version bumping rules.

What are the rules for patch and minor version increments in Tampermonkey userscripts?

The rules for patch and minor version increments in Tampermonkey userscripts are deterministic, meaning version bumps follow strict, predictable logic. This ensures consistent @version header updates across all your scripts before every commit.

How do I keep @name and @version headers in sync across multiple Tampermonkey scripts?

To keep @name and @version headers in sync across multiple Tampermonkey scripts, this skill automatically validates and updates the headers whenever a .user.js file changes. It enforces consistency before allowing the commit to complete.