babel-copy-optimizer

To fix translation-layout defects from a babel-copy QA report, this Skill identifies the latest unhandled failed qa-report.json, extracts its remediation items, and applies targeted changes to the babel-copy pipeline or per-document overrides. It then reruns the pipeline into a fresh timestamped output directory to verify fixes.

Automating translation pipeline remediation involves converting failed QA remediation notes into concrete code changes and auto-iterating on defects. This Skill closes the loop by rerunning babel-copy until goals are met, tracking progress, and producing a documented optimizer outcome in both human-readable and machine-readable formats.

To generate optimizer reports after rerunning a failed translation pipeline, this Skill produces a human-readable optimizer-report.md next to the handled QA artifacts. When appropriate, it also generates a machine-readable optimizer-report.json summarizing the remediation attempts and outcomes.

Yes, you can auto-iterate on per-document overrides without manual code changes. The optimizer extracts remediation items from the failed QA report and applies targeted changes directly to per-document overrides or the babel-copy pipeline configuration before rerunning into a new timestamped output directory.

If your translation pipeline still fails after applying remediation notes, you may need to re-QA the fresh timestamped output directory to verify actual remediation progress. This Skill handles the iteration loop by checking the new results and documenting the remaining or resolved defects in an optimizer-report.

Yes, you need a failed qa-report.json file in your workspace to automate babel-copy defect remediation. The Skill identifies the latest unhandled failed QA report with this specific format to extract remediation items and apply targeted pipeline or per-document changes.