config-hygiene

Fix repository config by analyzing and correcting `.gitignore` entries, ESLint configurations, and package.json scripts. This targets unignored backup files, duplicated linting rules, and silent hook failures, ensuring project consistency and reducing maintenance overhead.

Your `.gitignore` fails to exclude backup files due to missing patterns. Analyzing `.gitignore` entries detects and adds missing patterns to keep your repository clean, preventing common build artifacts and editor temporary files from being accidentally committed.

Stop silent failures in npm prepare hook scripts by validating package.json scripts. Hook script validation ensures that essential scripts like `prepare` do not fail silently, catching configuration issues that would otherwise disrupt project consistency and maintenance.

Yes, this config hygiene check works with existing ESLint configurations by identifying and suggesting fixes for duplicated plugin definitions and excessive disabled rules. It analyzes your current setup to ensure project consistency without requiring a full configuration rewrite.

The best way to identify missing `.gitignore` patterns is to run a dedicated config hygiene check script. This process analyzes your `.gitignore` entries to detect and add missing patterns, keeping your repository clean and free of unignored backup files and build artifacts.

Common configuration hygiene issues in a JavaScript repository include incorrect `.gitignore` patterns, duplicated ESLint configurations, and silent failures in hook scripts. Resolving these issues ensures a cleaner, more maintainable codebase with reduced maintenance overhead.