review-and-release

Synchronize README.md and plugin metadata with agents and skills.

11|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/ivklgn/ai --skill review-and-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-and-release
Source: https://github.com/ivklgn/ai/tree/main/.claude/skills/review-and-release
Command: npx skills add https://github.com/ivklgn/ai --skill review-and-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the repository README.md and plugin metadata in sync with the current set of agents and skills, and ensures plugin conventions are followed before a release.

Core Features & Use Cases

  • Inventory and diff agents and skills from claude/agents and claude/skills.
  • Validate plugin conventions (frontmatter, fields, versioning) and produce a release-ready state.
  • Bump the patch version and commit the release automatically.

Quick Start

Execute the /review-and-release command to audit, sync, and prepare a release.

Frequently Asked Questions about review-and-release

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

FAQPage Schema
How do I automate README.md synchronization with my current agents and skills inventory?

Automating README.md synchronization involves scanning the claude/agents and claude/skills directories to inventory components, diffing the existing README.md, and updating documentation to accurately reflect the current repository structure.

What is the best way to validate plugin conventions and frontmatter before a release?

Validating plugin conventions requires enforcing required frontmatter fields and structural rules across agents and skills. You can automate this validation process to ensure metadata complies with versioning standards before preparing a release-ready commit.

How do I automatically bump the patch version and generate a release commit?

Automatically bumping the patch version and generating a release commit involves running a synchronization workflow that validates plugin conventions, updates metadata, and prepares the repository state for release upon successful validation.

Can I diff repository documentation against my actual skills and agents directory?

Yes, diffing repository documentation against actual directories is possible by scanning the claude/agents and claude/skills folders, comparing the discovered inventory with the README.md, and identifying discrepancies to synchronize the documentation.

Does automated release validation enforce required frontmatter fields for all components?

Automated release validation enforces required frontmatter fields and structure for all components. It scans your agents and skills to ensure every piece of metadata meets the defined plugin conventions before allowing a version bump.

When should I not use an automated repository synchronization and release workflow?

Automated repository synchronization and release workflows should be avoided when you need manual control over versioning increments beyond patch levels, or when your repository structure does not utilize the claude/agents and claude/skills directory conventions.