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.