refreshing-artifacts

To re-validate artifact metadata and refresh confidence data, invoke the /refresh command with an artifact path. The skill routes to the appropriate validation logic and updates the artifact frontmatter with new confidence inputs.

No, re-validation does not overwrite computed confidence scores. The process specifically preserves your existing computed scores while updating metadata like last_validated_at, last_validated_commit, and validation_count.

To initialize confidence tracking for artifacts missing validation metadata, use the /refresh command with the artifact path. The skill automatically initializes the required confidence metadata fields and persists them directly to the frontmatter.

Yes, you can use the same workflow for user-canvas, journey, reality, and taste artifacts. The skill automatically routes to the correct specialized re-validation logic based on the specific artifact type provided.

Before triggering artifact re-validation, you need access to the artifact frontmatter, the current git state, and the ability to route to specialized re-validation skills based on artifact type.