x-commit-planning

You can batch commit planning artifacts under whitelisted paths like ai/epics/epic-XXXX/** and plans/** to bypass heavy code formatting, preserving a clean working tree while maintaining an auditable Git history.

Standard pre-commit hooks often fail on planning documents because they enforce code compilation or formatting rules. This Skill skips the code pre-commit chain entirely, applying only argument validation and conventional commit standards.

No, you cannot commit source code files. The Skill enforces safe usage with explicit path whitelists, restricting commits to planning artifacts under ai/epics/epic-XXXX/** and plans/** to prevent accidental commits of binaries or source code.

The best way to ensure an atomic Git history is to batch all planning outputs into a single conventional commit. This Skill validates your epic-id format, checks whitelisted paths, enforces subject length, and runs git add for a unified commit.

Yes, epic-id format validation is automatically enforced by the workflow before executing git add. This ensures your planning artifacts are correctly identified and traceable within the coordinated planning workflows.

You should use a pre-commit bypass when you need to commit planning artifacts like epics, stories, and templates as a single unit. This skips code linting and compilation chains while still producing a traceable and auditable record.