ignore-files-workflow

Synchronizing ignore files aligns entries between .gitignore and .dockerignore to maintain consistent exclusion rules across Git and Docker contexts. This Skill automates cross-file synchronization with alphabetical ordering and section-based grouping, ensuring patterns stay aligned and reducing the risk of exposing secrets or inflating build context.

Organize patterns alphabetically within sections with descriptive comments to improve maintainability and scanning. This Skill enforces case-sensitive ASCII ordering, groups related rules by section, and documents each pattern's purpose, making ignore files predictable and easier to audit.

.dockerignore controls the build context sent to Docker, while .gitignore controls version control. Managing them separately prevents secrets and unnecessary files from entering containers. Synchronizing both files ensures consistent exclusion logic while respecting each tool's specific scope.

Prevent secret leakage by documenting specific patterns in .dockerignore with testing guidelines to verify exclusion. This Skill maintains precise, documented ignore rules across Docker and Git contexts, reducing the risk of exposing credentials or sensitive data in built images.

Yes. This Skill automates management of .gitignore, .dockerignore, and supporting documentation by enforcing consistent patterns, alphabetical ordering, and cross-file synchronization. Automation reduces manual errors and keeps ignore rules predictable as your project evolves.

Test ignore patterns to verify that intended files are excluded and critical files are included in both Git and Docker contexts. This Skill includes testing guidelines to ensure predictable build contexts and confirm that secrets and unnecessary artifacts remain excluded.