From d8fa5c4cd1fd5e42ee785027e29cd149c5eebf1f Mon Sep 17 00:00:00 2001 From: Shirone Date: Fri, 23 Jan 2026 18:34:11 +0100 Subject: [PATCH] feat: Add commit step template for conventional commits - Introduced a new pipeline step template for committing changes, emphasizing the use of conventional commit format. - The template includes detailed instructions for reviewing changes, creating a commit message, and executing the git commit command. - Ensures that all commits follow a consistent pattern for better changelog generation and project management. - Updated the index to include the new commit template in the pipeline step templates. --- .../dialogs/pipeline-step-templates/commit.ts | 150 ++++++ .../dialogs/pipeline-step-templates/index.ts | 2 + docs/prd-to-features-guide.md | 431 ++++++++++++++++++ 3 files changed, 583 insertions(+) create mode 100644 apps/ui/src/components/views/board-view/dialogs/pipeline-step-templates/commit.ts create mode 100644 docs/prd-to-features-guide.md diff --git a/apps/ui/src/components/views/board-view/dialogs/pipeline-step-templates/commit.ts b/apps/ui/src/components/views/board-view/dialogs/pipeline-step-templates/commit.ts new file mode 100644 index 00000000..8908706e --- /dev/null +++ b/apps/ui/src/components/views/board-view/dialogs/pipeline-step-templates/commit.ts @@ -0,0 +1,150 @@ +export const commitTemplate = { + id: 'commit', + name: 'Commit Changes', + colorClass: 'bg-purple-500/20', + instructions: `## Commit Changes Step + +# ⚠️ CRITICAL REQUIREMENT: YOU MUST COMMIT ALL CHANGES USING CONVENTIONAL COMMIT FORMAT ⚠️ + +**THIS IS NOT OPTIONAL. YOU MUST CREATE AND EXECUTE A GIT COMMIT WITH ALL CHANGES.** + +This step requires you to: +1. **REVIEW** all changes made in this feature +2. **CREATE** a conventional commit message +3. **EXECUTE** the git commit command + +**You cannot complete this step by only reviewing changes. You MUST execute the git commit command.** + +--- + +### Phase 1: Review Phase +Review all changes made in this feature: + +- Review all modified files using \`git status\` and \`git diff\` +- Identify the scope and nature of changes +- Determine the appropriate conventional commit type +- Identify any breaking changes that need to be documented + +--- + +### Phase 2: Commit Phase - ⚠️ MANDATORY ACTION REQUIRED ⚠️ + +**YOU MUST NOW CREATE AND EXECUTE A GIT COMMIT WITH ALL CHANGES.** + +**This is not optional. You must stage all changes and commit them using conventional commit format.** + +#### Conventional Commit Format + +Follow this format for your commit message: + +\`\`\` +(): + + + +