contentrain-validate-fixlisted

# Skill: Validate and Fix Content Issues > Diagnose validation failures, apply safe fixes, and re-check the project. --- ## When to Use Use this when: - validation reports errors or warnings - the user asks to fix schema/content issues - a write operation succeeded but the project still needs verification --- ## Steps ### 1. Run Validation Call `contentrain_validate` first. Group results into: - schema/type errors - missing required fields - relation integrity problems - locale completeness issues - canonical format warnings ### 2. Decide Auto-fix vs Manual Fix Auto-fix candidates: - canonical formatting - orphan metadata cleanup - stray non-i18n meta layout (an `i18n: false` model with per-locale meta files left by older versions) — pruned or migrated deterministically, never merging or downgrading a status - `publish_at`/`expire_at` copies an older `content_save` left in document frontmatter — stripped only when the meta record holds the same key, so the value is never lost and an author's own frontmatter field is never touched - a missing model `title_field` — backfilled by the same ranking Studio's title resolver uses (required name-like field first; slug/url/code never inferred), reported as a notice naming the rule. Read it: if the pick is wrong, correct it with `contentrain_model_save` - structural housekeeping reported by the validator Manual fix candidates: - missing required content - wrong field values - broken relations - incorrect sl