registry.diff

Compare skill and agent versions to classify changes and recommend actions.

2|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/epieczko/betty --skill registry-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: registry.diff
Source: https://github.com/epieczko/betty/tree/main/skills/registry.diff
Command: npx skills add https://github.com/epieczko/betty --skill registry-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml.

What problem does it solve?

Compare current and previous versions of skills/agents against their registries to detect changes, assess risk, and propose versioning and action recommendations.

Core Features & Use Cases

  • Determine diff type: new, version_bump, version_downgrade, permission_change, breaking_change, etc.
  • Compute recommended action: register, review, reject, or skip
  • Return detailed changed_fields and breaking indicators
  • Useful for CI/CD pipelines and governance

Quick Start

./skills/registry.diff/registry_diff.py path/to/skill.yaml

Frequently Asked Questions about registry.diff

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

FAQPage Schema
How do I detect breaking changes between skill versions in CI/CD?

Registry.diff compares current and previous skill versions to identify breaking changes, permission shifts, and status modifications. It classifies diff types and outputs actionable guidance with standardized JSON and exit codes for pipeline integration.

What changes does a skill version comparison detect?

Version comparison identifies new skills, version bumps or downgrades, permission changes, breaking changes, and field modifications. It tracks which fields changed and assesses risk impact for governance and validation workflows.

Can I use skill diffing to validate registry submissions?

Yes. Registry.diff parses skill manifests, performs registry lookups, and recommends actions—register, review, reject, or skip—based on detected changes and breaking indicators, supporting CI/CD governance pipelines.

What input format does skill version diffing require?

Skill diffing requires YAML manifest files as input. The tool parses the manifest, compares it against the registry, and outputs structured JSON with change details and recommended actions.

When should I skip version validation in CI/CD?

Skip validation when changes are non-breaking and don't affect permissions or status. Registry.diff classifies required actions; skip recommendations occur when detected changes pose no governance risk.