Conventional commit message format rules with story/ticket references
Follow the conventional commits format with story/ticket references:
<type>(<scope>): <description>
feat: new featurefix: bug fixdocs: documentation changesstyle: formatting, missing semicolons, etc.refactor: code change that neither fixes a bug nor adds a featuretest: adding missing tests or correcting existing testschore: changes to build process or auxiliary toolsPROJ-24, PROJ-5)config, scripts, infra)feat(PROJ-24): add epic/story structure, execution plan and initial implementation
fix(PROJ-25): resolve authentication error in bootstrap script
docs(PROJ-5): update setup instructions for new deployment process
chore(config): update required APIs list for infrastructure