# Gaf Shared Library Release Guard

> Enforces GAF shared library governance by preventing edits to published versions and guiding semver release flow for new versions. Use when changing shared clients or utilities under shared/ folders.

- Skill: `miguel-carrera/gaf-shared-library-release-guard` (Agent Skill)
- Install (CLI): `npx skillmds@latest add miguel-carrera/gaf-shared-library-release-guard`
- Raw SKILL.md: https://api.skillmd.com/api/skills/miguel-carrera/gaf-shared-library-release-guard/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: miguel-carrera (https://skillmd.com/u/miguel-carrera)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/miguel-carrera/gaf-shared-library-release-guard

---


# GAF Shared Library Release Guard

## Goal
Keep published shared library versions immutable and ensure safe versioned releases.

## Use This Skill When
- Editing shared clients/utilities.
- Preparing to publish a new shared library version.
- Reviewing shared library PRs.

## Governance Rules
- Published version folders are immutable.
- New changes happen in development area (`shared/<category>/<lib-name>`), then published via `node scripts/publish-library.js <category> <library_name> [major|minor|patch]` from `gaf-core-knowledge/`.
- Version bumps should follow semantic versioning intent.
- Task manifests must reference the versioned folder (e.g. `clients/log-writer_v1.0.0`), not the dev folder name alone.

## Checks
- Detect edits inside published versioned directories.
- Confirm release notes/changelog intent is present.
- Verify dependents can migrate to new version path/reference.

## Output
- `Compliant` or `Violation`.
- required corrective actions (if violation).
- recommended release version bump and rationale.

## Guardrails
- Never silently overwrite published versions.
- If versioning structure is ambiguous, ask for explicit release decision.