ai-standardize-release

To preserve custom semantic-release configurations, this Skill detects existing settings in pyproject.toml or .releaserc.json and classifies them as canonical, drifted, or custom before merging. It interactively prompts for user decisions to ensure safe configuration standardization.

Yes, config standardization works with both Python and Node projects. It parses Python configurations from pyproject.toml and Node configurations from .releaserc.json or package.json, ensuring cross-validation with commit-scheme.json across both ecosystems.

You can merge canonical templates safely by running the standardization tool, which analyzes existing configs and categorizes fields. It writes merged configurations only after user approval, reapplying your customizations to prevent unintended data loss.

Standardizing semantic-release configs requires interactive prompts to ensure changes are intentional. When drift is detected between your repository and the canonical template, prompting classifies fields and confirms user decisions before writing merged configs, preventing unintended overwrites.

Yes, you can use this tool to cross-validate semantic-release settings with commit-scheme.json. It enforces TOML parsing and validates existing configurations against the commit scheme before safely merging any canonical template changes.