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

ai-standardize-precommit

Standardize pre-commit configurations with drift detection and user confirmation.

1|Updated Apr 2, 2026
Search Tags:#automation#configuration#pre-commit#code-quality#drift-detection#git-hooks#ask-user
One-click install
npx skills add https://github.com/svange/augint-shell --skill ai-standardize-precommit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-standardize-precommit
Source: https://github.com/svange/augint-shell/tree/main/.agents/skills/ai-standardize-precommit
Command: npx skills add https://github.com/svange/augint-shell --skill ai-standardize-precommit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects drift in pre-commit/hook configurations and asks for user confirmation before writing canonical templates, preventing accidental overwrites of custom hooks.

Core Features & Use Cases

  • Drift detection for Python (.pre-commit-config.yaml) and Node (husky + lint-staged) environments.
  • Ask-before-writing workflow that requires explicit user confirmation via AskUserQuestion before merging changes.
  • Generates and merges canonical templates while preserving user customizations, with a clear path for merging.

Quick Start

Run the standardize command for your repository path to reconcile pre-commit configurations with the canonical template.

Frequently Asked Questions about ai-standardize-precommit

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

FAQPage Schema
How do I prevent accidental overwrites of my pre-commit hooks?▼

You can prevent accidental overwrites by detecting configuration drift against a canonical template and requiring explicit user confirmation before merging any pre-commit hook changes.

What is pre-commit configuration drift and how does it affect Python and Node projects?▼

Pre-commit configuration drift occurs when .pre-commit-config.yaml in Python or husky and lint-staged in Node projects diverge from standard templates, risking inconsistent code quality checks across the repository.

How do I standardize .pre-commit-config.yaml without losing custom hooks?▼

You can standardize .pre-commit-config.yaml without losing custom hooks by comparing current settings against a canonical template, generating a merge path, and approving changes via an interactive ask-before-acting workflow.

Does this pre-commit standardization workflow support both husky and lint-staged for Node?▼

Yes, the standardization workflow supports Node environments by targeting both husky and lint-staged configurations to detect drift and orchestrate template merges.

Can I automate pre-commit configuration merges while still manually confirming changes?▼

Yes, you can automate configuration merges while manually confirming changes by enforcing an ask-before-acting workflow that uses interactive prompts to require explicit approval before writing templates.

Related Skills

Explore More Software Engineering Skills→
yashs33244yashs33244
1

setup-pre-commit

Set up Husky pre-commit hooks with lint-staged and Prettier for Node.js repositories.

Community
Intermediate
Hyeonjun0527Hyeonjun0527
1

validate

Run lint, format, typecheck, and build verification pipelines on code changes.

Community
Intermediate
MolcajeteAIMolcajeteAI
2

pre-commit-hooks

Configure Husky and lint-staged pre-commit hooks for automated code quality checks.

Official
Intermediate
killvxkkillvxk
3

team-load

Loads saved team configurations from .team-profiles in template or snapshot formats.

Community
Intermediate