release-yamls

Automate knowledge base releases with version bumps, CHANGELOG updates, and cache refresh.

4|Updated Aug 14, 2025
One-click install
npx skills add https://github.com/ironsheep/P2-Knowledge-Base --skill release-yamls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-yamls
Source: https://github.com/ironsheep/P2-Knowledge-Base/tree/main/.claude/skills/release-yamls
Command: npx skills add https://github.com/ironsheep/P2-Knowledge-Base --skill release-yamls

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the release process for the P2 knowledge base YAMLs, ensuring consistency and accuracy in versioning, CHANGELOG updates, and local cache refresh.

Core Features & Use Cases

  • Version Management: Bump the version number and update the README badge and CHANGELOG.
  • Two-Commit Release: Ensures the correct order of content and derived artifact commits.
  • Pre-commit Validation: Checks for clean YAML maintenance and correct version bumping.
  • Index Regeneration: Generates the published index and AI reference after content commit.
  • Post-commit Validation: Validates the index and AI reference before pushing.
  • Tagging and Pushing: Tags the index commit and pushes it to the repository.
  • Cache Refresh: Refreshes the local p2kb-mcp cache after push.
  • Impact Survey: Flags consuming manuals for re-audit if necessary.

Quick Start

Use the release-yamls skill to release a new version of the P2 knowledge base.

Frequently Asked Questions about release-yamls

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

FAQPage Schema
How do I automate YAML knowledge base release workflows with git and Python?

You can automate this by using a Skill that bumps versions, updates the CHANGELOG and README badge, and manages a two-commit release process for content and derived artifacts using git and Python.

What is the correct process for version bumping and CHANGELOG updates in a knowledge base release?

The correct process requires pre-commit validation for clean YAML, bumping the version, updating the CHANGELOG and README badge, and then committing content before regenerating the index and AI reference.

Do I need Python and git installed to run automated knowledge base version control tasks?

Yes, automated knowledge base release management requires git for version control operations like tagging and pushing, alongside various Python libraries for artifact generation and index regeneration.

How to validate YAML content and regenerate indexes before pushing a knowledge base release?

You validate by running pre-commit checks for clean YAML, committing content changes, regenerating the published index and AI reference, and then performing post-commit validation before tagging and pushing.

What are the limitations of automating P2 knowledge base YAML releases?

Limitations include strict adherence to a two-commit release order, dependency on specific Python libraries for artifact generation, and the necessity of refreshing the local p2kb-mcp cache after pushing.

When should I refresh the local cache after a knowledge base release?

Refresh the local cache immediately after pushing the tagged index commit to the repository, which also flags consuming manuals for re-audit if necessary.