skills.rest
svange
svangeCOMMUNITY
Explore all skills by this author →
GitHub

ai-standardize-dotfiles

Detect drift in dotfiles and merge canonical templates with user confirmation.

1|Updated Apr 2, 2026
Search Tags:#dotfiles#interactive#risk-mitigation#gitignore#config-management#editorconfig#template-merge
One-click install
npx skills add https://github.com/svange/augint-shell --skill ai-standardize-dotfiles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-standardize-dotfiles
Source: https://github.com/svange/augint-shell/tree/main/.agents/skills/ai-standardize-dotfiles
Command: npx skills add https://github.com/svange/augint-shell --skill ai-standardize-dotfiles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect drift between a repository's dotfiles and the canonical templates, and ensure changes are made safely.

Core Features & Use Cases

  • Detect drift in .editorconfig and .gitignore against canonical templates.
  • Prompt for user confirmation before overwriting any custom entries.
  • Merge canonical templates while preserving repo-specific patterns.

Quick Start

Run uv run ai-tools standardize <repo-path> to detect drift and apply canonical templates with your approved custom entries.

Frequently Asked Questions about ai-standardize-dotfiles

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

FAQPage Schema
How do I detect dotfile drift between my repository and canonical templates?▼

To standardize dotfiles, run the standardize command with your repository path to detect drift, then use the interactive decision flow to approve merging canonical templates while preserving your repo-specific custom gitignore and editorconfig entries.

Can I merge canonical gitignore templates without losing repo-specific custom entries?▼

Merging canonical gitignore templates preserves repo-specific custom entries by prompting for user confirmation before overwriting, ensuring your project-specific ignore patterns remain intact while applying standard configurations.

What is interactive dotfile standardization and when do I need it?▼

Interactive dotfile standardization is an ask-first configuration management process that identifies drift in .editorconfig and .gitignore files, prompting before overwriting to ensure safe, auditable updates across multiple repositories.

Do I need canonical editorconfig and gitignore templates before using this standardization process?▼

Canonical editorconfig and gitignore templates are required as bases for the standardization process, providing the reference configurations needed to detect drift and merge updates while preserving repository-specific custom entries.

What happens to custom editorconfig entries when applying canonical templates?▼

Custom editorconfig entries are preserved when applying canonical templates through an interactive decision flow that prompts for user confirmation before overwriting any existing repo-specific configurations, ensuring safe and auditable updates.

Related Skills

Explore More Software Engineering Skills→
thatrebeccaraethatrebeccarae
97

repo-scaffold

Initialize GitHub repositories with standard files and configurations.

Community
Intermediate
hackefellerhackefeller
1

jinn-project-init

Bootstrap project templates, install dependencies, configure tooling, and initialize Git.

Official
Advanced
robertbr123robertbr123

requesting-code-review

Automate code review with security scans, quality checks, and automated fixes.

Community
Advanced
memoirlabsmemoirlabs
6

bun-init

Initialize a Bun project with TypeScript and production-friendly configuration.

Official
Intermediate