jfrog-reconcile-manifest

Reconcile JFrog Platform state with a desired-state manifest.

5|1|Updated Mar 2, 2026

Search Tags:#platform #manifest #diff #state-management #reconcile #jfrog

Ready to run

npx skills add https://github.com/jfrog/ai-agent-examples --skill jfrog-reconcile-manifest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jfrog-reconcile-manifest
Source: https://github.com/jfrog/ai-agent-examples/tree/main/onboarding-workflows/skills/jfrog-reconcile-manifest
Command: npx skills add https://github.com/jfrog/ai-agent-examples --skill jfrog-reconcile-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile JFrog Platform state with a desired-state manifest. Reads current configuration, computes a diff, presents changes for approval, and applies only the delta. Use when the user wants to update, sync, or reconcile JFrog with manifest changes.

Core Features & Use Cases

Supports 3-way diff when a baseline exists (baseline vs manifest vs live) and 2-way diff when no baseline is available, enabling safe planning before applying changes.
Handles projects, repositories, members, OIDC, and Xray/curation settings, with a structured change taxonomy (CREATE, UPDATE, FLAG, etc.) and explicit user confirmation where deletion isn’t automatic.
Integrates with state backends (Artifactory or git) to retrieve baseline manifests and persist the resulting current state after reconciliation.

Quick Start

Provide a manifest describing the desired state and let me plan and apply only the delta to reconcile the JFrog Platform.

Frequently Asked Questions about jfrog-reconcile-manifest

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

FAQPage Schema

How do I reconcile JFrog Platform state with a desired-state manifest?▼

To reconcile JFrog Platform state, you provide a manifest path and loaded credentials so the skill can compute a diff against live APIs and apply only the user-approved delta. It reads current configuration, presents changes for approval, and updates projects, repositories, members, OIDC, and Xray settings.

What is the difference between 2-way and 3-way diff when syncing JFrog configuration?▼

A 3-way diff compares a baseline, manifest, and live state for safer planning, while a 2-way diff compares only the manifest against live state when no baseline exists. Both identify deltas across projects, repositories, members, OIDC, and Xray settings before applying changes.

How do I apply manifest changes to JFrog projects and repositories?▼

You apply manifest changes by providing the manifest path to trigger a diff against the live JFrog Platform. The skill generates a structured taxonomy of changes (CREATE, UPDATE, FLAG) and requires explicit user confirmation before applying the delta to projects and repositories.

Does JFrog reconciliation support state backends like Artifactory and git?▼

Yes, JFrog reconciliation integrates with Artifactory or git state backends to retrieve baseline manifests and persist the resulting current state after reconciliation. This enables 3-way diff computation when a baseline is available.

Why does JFrog manifest reconciliation flag certain changes instead of deleting them automatically?▼

JFrog manifest reconciliation flags certain changes instead of deleting them automatically to ensure explicit user confirmation for destructive actions. The skill uses a structured change taxonomy including CREATE, UPDATE, and FLAG, requiring user approval where deletion isn't automatic.

Can I update JFrog Xray and OIDC settings using a desired-state manifest?▼

Yes, you can update JFrog Xray and OIDC settings by including them in your desired-state manifest. The reconciliation skill computes deltas for these settings alongside projects, repositories, and members, then applies the approved changes to the live JFrog Platform.