ignore-files-workflow

Synchronizing .gitignore and .dockerignore files requires maintaining parity for common patterns to prevent accidental commits and optimize Docker build contexts. This Skill enforces synchronization rules, alphabetical ordering, and organizational best practices automatically.

Organizing ignore files for a clean repository involves enforcing alphabetical ordering, section organization, and pattern specificity. This Skill manages version control and Docker build context by applying specific pattern inclusion and exclusion guidelines.

Docker build context includes unnecessary files when .dockerignore lacks proper synchronization with .gitignore. This Skill addresses build context management by enforcing organizational best practices and maintaining parity for common exclusion patterns.

A separate .dockerignore is needed alongside .gitignore to optimize Docker build contexts and prevent accidental commits. This Skill synchronizes both files for common patterns while addressing their distinct version control and build context requirements.

Applying alphabetical ordering and best practices to existing ignore files enforces consistency and organization. This Skill reorganizes current .gitignore and .dockerignore files by applying specific pattern inclusion and exclusion guidelines.

A synchronized ignore file workflow is not suitable when .gitignore and .dockerignore require fundamentally distinct exclusion patterns. This Skill maintains parity for common patterns but requires adherence to specific inclusion and exclusion guidelines for distinct requirements.