tag-release

Create annotated Git tags for version milestones and data collection events.

4|1|Updated Jan 8, 2024
One-click install
npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill tag-release-opensourcepharmafoundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tag-release
Source: https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg/tree/main/.claude/skills/tag-release
Command: npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill tag-release-opensourcepharmafoundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents lost context and inconsistent versioning by helping you create clear, annotated Git tags for releases and data-collection milestones.

Core Features & Use Cases

  • Semver version tags: Create annotated tags like v1.2.3 with a structured changelog describing changes since the previous tag.
  • Data collection tags: Create annotated tags in the data/ namespace (e.g., data/chembl-full-YYYY-MM-DD) summarizing what was collected.
  • Guardrails and confirmation: Inspects existing tags and changes since the latest tag, proposes the best next tag name/message, and asks for confirmation before creating or pushing.

Quick Start

Ask to create the next release tag with a message summarizing changes since the most recent tag, then confirm when prompted.

Frequently Asked Questions about tag-release

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

FAQPage Schema
How do I create annotated git tags for software releases?

Annotated git tags for software releases are created locally using the git tag -a command, generating a structured changelog message that summarizes code changes since the previous milestone. This ensures consistent versioning documentation without automatically pushing to remote repositories.

What is the best way to generate semantic versioning tags with a changelog?

Semantic versioning tags like v1.2.3 are generated by inspecting existing repository tags and determining the appropriate version bump. A changelog-style annotation is then produced automatically, describing the specific changes committed since the most recent release tag.

How do I tag data collection events in a version control pipeline?

Data collection events are tagged using a data/ namespace format, such as data/chembl-full-YYYY-MM-DD. This approach captures dated dataset import milestones within version control, summarizing exactly what information was collected during that specific pipeline run.

Can I list and compare existing git tags before creating a new release?

Existing git tags can be listed and compared before creating a new release. The workflow inspects current tags and evaluates repository changes since the latest milestone to propose the most accurate next tag name and annotation message.

Does this release tagging process push annotated tags to a remote repository automatically?

Annotated tags are not pushed to a remote repository automatically. Guardrails require explicit user confirmation before any local tag creation or remote pushing occurs, ensuring full control over version control distribution.