tag-audit

Audit package.json version alignment with local and remote git tags.

1|2|Updated Apr 6, 2026

Search Tags:#release-management #ci-cd #semantic-release #version-control #tag-audit #npm-packages #tag-misalignment

Ready to run

npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill tag-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tag-audit
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/tag-audit
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill tag-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit tag/version misalignment that leads to release conflicts and deploy drift. Works for npm packages and app deployments.

Core Features & Use Cases

Detects mismatches between package.json version, local tags (vX.Y.Z), and remote tags to surface drift
Supports both npm package releases and app deploys, with guidance for fixed tags, semantic-release or manual workflows
Provides a step-by-step audit procedure and remediation suggestions for common scenarios like missing tags, tag at wrong commit, or version gaps

Quick Start

Use this skill to verify that your package.json version aligns with the latest local and remote tags and fix discrepancies before releases.

Frequently Asked Questions about tag-audit

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

FAQPage Schema

How do I check if package.json version matches local and remote git tags?▼

To check tag and version alignment, you need to audit your package.json version against local and remote git tags. This process surfaces mismatches like missing tags or version gaps to prevent release conflicts and deploy drift.

Why does semantic-release cause tag misalignment during npm package deployments?▼

Semantic-release can cause tag misalignment when package.json versions, local tags, and remote tags fall out of sync. Auditing these components detects drift and provides remediation steps for common scenarios like tags pointing to wrong commits.

What is the best way to prevent release drift in CI/CD pipelines?▼

The best way to prevent release drift in CI/CD pipelines is conducting regular tag audits. By verifying consistency between package.json and remote tags before releases, you can detect and fix version misalignment early.

Does tag auditing work with manual version control workflows?▼

Yes, tag auditing works with both semantic-release and manual workflows. It inspects package.json versions alongside local and remote tags to provide remediation suggestions for discrepancies, fitting both npm packages and app deployments.

When do I need to audit git tags for version control?▼

You need to audit git tags for version control during pre-release checks, post-release validations, and ongoing health audits. This ensures package.json versions align with local and remote tags to prevent deploy drift.

How to fix missing git tags pointing to wrong commits before a release?▼

To fix missing git tags or tags at wrong commits before a release, run an audit to detect mismatches between package.json and remote tags. The audit provides step-by-step remediation suggestions to resolve these specific drift scenarios.