ai-standardize-release

Detect and preserve custom semantic-release configurations before merging canonical templates.

1|Updated Apr 2, 2026

Search Tags:#automation #versioning #python #nodejs #semantic-release #config-management

Ready to run

npx skills add https://github.com/svange/augint-shell --skill ai-standardize-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ai-standardize-release
Source: https://github.com/svange/augint-shell/tree/main/.agents/skills/ai-standardize-release
Command: npx skills add https://github.com/svange/augint-shell --skill ai-standardize-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects when a repository's semantic-release configuration would be overwritten by a canonical template and preserves user-defined customizations, preventing unintended changes.

Core Features & Use Cases

Detects Python (pyproject.toml [tool.semantic_release]) and Node (.releaserc.json or package.json release) configurations and classifies fields as canonical, drifted, or custom.
Interactively prompts for user decisions when drift is detected, ensuring intentional changes.
Merges configurations safely, preserving content outside the canonical section and reapplying within-section customizations after confirmation.

Quick Start

Run uv run ai-tools standardize <path> to merge the canonical semantic-release template with your repository's existing config, preserving user customizations after confirmation.

Frequently Asked Questions about ai-standardize-release

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

FAQPage Schema

How do I preserve custom semantic-release configurations before overwriting with a canonical template?▼

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.

Does the config standardization process work with both Python and Node projects?▼

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.

How do I merge a canonical semantic-release template without losing my drifted config fields?▼

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.

Why does standardizing semantic-release configs require interactive prompts for drifted fields?▼

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.

Can I use this tool to cross-validate semantic-release settings with commit-scheme.json?▼

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.