kata-ahrena-version

Resolve the installed Ahrena framework version from local files or git tags.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-ahrena-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kata-ahrena-version
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-ahrena-version
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-ahrena-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork of determining which Ahrena framework version is installed by consistently resolving the version string from local sources at runtime or build time.

Core Features & Use Cases

  • Consumer-mode resolution: Reads .ahrena/.version relative to the current working directory and emits its literal contents (including non-SemVer values like branch names) when present and non-empty.
  • Dev-mode fallback: When .ahrena/.version is missing or empty, derives a stable version by using git describe --tags --abbrev=0, stripping a leading v when present.
  • Strict output validation: Ensures stdout is a single non-empty line that never begins with v, and fails with a clear, structured error to prevent downstream ambiguity.

Quick Start

Ask the AI to run kata-ahrena-version to output the resolved Ahrena framework version string to stdout, using .ahrena/.version when available and otherwise falling back to a local git describe result.

Frequently Asked Questions about kata-ahrena-version

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

FAQPage Schema
How do I resolve the Ahrena framework version locally without a network lookup?

To resolve the Ahrena framework version locally, the tool reads a local .ahrena/.version file or falls back to deriving a stable version from local git tags. This ensures you get a single plain-text version string to stdout without network dependencies.

What happens if the .ahrena/.version file is missing during version resolution?

When the .ahrena/.version file is missing or empty, the resolution falls back to dev-mode by executing git describe --tags --abbrev=0. It strips the leading v from the git-derived tag to emit a valid version string.

Can I use git describe to get a SemVer compliant Ahrena build version?

Yes, you can use git describe to derive the version in dev-mode setups. The tool automatically strips the leading v from the git tag result to ensure the output version string never begins with v.

Why does local configuration version resolution fail and emit a structured error?

Local configuration version resolution fails and emits a structured error with a non-zero exit when local sources cannot be validated or are empty. This strict output validation prevents downstream ambiguity by ensuring stdout only contains a single non-empty line.