Prompt file imported from Coding-Krakken/NeuroLogix (.github/prompts/operations/git-commit.prompt.md). Copyright stays with the author.

Prompt: Git Commit

Name: git-commit
Author: Coding-Krakken

Category: operations
Purpose: Guide agents to commit code changes properly
Complexity: Simple
Expected Duration: 2-5 minutes

Objective

Commit code changes to git with proper conventional commit messages, ensuring all quality gates pass before committing.

Context

You are an AI agent in a 27-agent engineering organization. Your team uses strict git workflows with conventional commits and quality gates. Every commit must:

Pass local quality gates (lint, typecheck, test)
Use conventional commit message format
Reference the GitHub issue number
Include only related files (≤5 files per commit)

Input

Provide:

Files to commit (absolute paths)
Commit type (feat, fix, refactor, docs, test, chore, security, perf)
Scope (seo, cart, checkout, payment, api, ui, etc.)
Subject (≤72 chars, imperative mood)
Body (optional, detailed explanation)
Issue number (e.g., #42)

Execution Steps

Step 0: Git Context Preflight (MANDATORY)

Capture current repository state before making or committing changes:

git branch --show-current
git status --short
git log -1 --oneline

Include this snapshot in your work notes or issue comment.

Step 1: Pre-Commit Quality Gates

Run these commands and ensure they ALL pass:

# Hook-equivalent local gate (fast mode)
npm run hook:precommit

# Optional strict CI-parity gate
npm run hook:precommit:ci

If any fail: Fix issues before proceeding.

Step 2: Stage Files

Stage ONLY the files you changed for this specific task:

git add <file1> <file2> <file3>

# Example:
git add src/lib/seo/metadata.ts src/lib/seo/__tests__/metadata.test.ts

Verify staged files:

git status

Step 3: Craft Commit Message

Format:

<type>(<scope>): <subject>

<body (optional)>

<footer>

Example 1: Feature commit

feat(seo): enforce INV-SEO-1 metadata length constraints

- Title truncated to ≤60 chars
- Description truncated to ≤160 chars
- Added unit tests for edge cases

Tests: 13 passing
Coverage: metadata.ts 100%

Issue #42

Example 2: Fix commit

fix(cart): prevent duplicate items in cart state

Resolves race condition when user double-clicks "Add to Cart" button.
Added debounce logic to addToCart mutation.

Fixes #123

Example 3: Test commit

test(sitemap): add coverage for INV-SEO-3 validation

Ensures sitemap includes all 481 active products.

Issue #42

Step 4: Commit

Step 3.5: Pre-Push Gate (Before `git push`)

Run the CI-like pre-push gate:

npm run hook:prepush

Optional strict mode:

npm run hook:prepush:ci

Step 4: Commit

Short message (≤72 chars total):

git commit -m "feat(seo): enforce INV-SEO-1 metadata constraints"

Multi-line message:

git commit -m "feat(seo): enforce INV-SEO-1 metadata constraints" -m "- Title ≤60 chars
- Description ≤160 chars
- Added unit tests

Tests: 13 passing
Coverage: metadata.ts 100%

Issue #42"

Step 5: Push to Remote

git push origin <branch-name>

# Example:
git push origin feature/42-seo-foundation

# Verify clean checkpoint state
git status --short

Step 6: Update GitHub Issue

After successful push, add a comment to the GitHub issue:

gh issue comment 42 --body "Committed metadata helpers (feat: enforce INV-SEO-1). Tests passing."

# Preferred detailed format:
gh issue comment 42 --body "Checkpoint update:\n\n- Branch: feature/42-seo-foundation\n- Commit: <short-sha>\n- Scope: metadata helpers\n- Checks: lint ✅, typecheck ✅, test ✅\n- Git status: clean\n- Next: proceed to next slice"

Commit Types Reference

Type	Usage	Example
`feat`	New feature or enhancement	`feat(seo): add BreadcrumbList schema`
`fix`	Bug fix	`fix(cart): prevent duplicate items`
`refactor`	Code restructuring (no behavior change)	`refactor(payment): extract validation`
`docs`	Documentation changes	`docs(readme): update setup instructions`
`test`	Adding or updating tests	`test(checkout): add e2e test for flow`
`chore`	Maintenance (deps, config, etc.)	`chore(deps): update Next.js to 16.1.7`
`security`	Security improvements/fixes	`security(auth): sanitize user input`
`perf`	Performance improvements	`perf(api): cache product catalog`
`style`	Formatting only (no code change)	`style(cart): format with Prettier`

Common Scopes

seo — SEO-related (metadata, sitemap, robots)
cart — Shopping cart
checkout — Checkout flow
payment — Payment processing
api — API routes
ui — UI components
store — State management (Zustand)
square — Square API integration
test — Test infrastructure
deps — Dependencies
config — Configuration files

Validation Checklist

Before committing:

All quality gates pass (lint, format, typecheck, test)
Only related files staged (≤5 files)
Commit message follows conventional format
Commit message references issue number
Subject line ≤72 chars
Subject uses imperative mood ("add" not "added")
Git context preflight captured (branch, status, head)

After committing:

Pushed to remote branch
GitHub issue commented with update
Post-push git status --short recorded
No secrets committed (.env, tokens, keys)

Anti-Patterns (DO NOT DO)

❌ Committing without running quality gates

git add .
git commit -m "quick fix"
# BAD: No quality gates run, might commit broken code

❌ Vague commit messages

git commit -m "updates"
git commit -m "misc changes"
git commit -m "fix"
# BAD: No context, no traceability

❌ Committing unrelated files together

git add src/lib/seo/metadata.ts src/app/api/checkout/route.ts
git commit -m "various updates"
# BAD: SEO and checkout are unrelated, should be separate commits

❌ Committing work-in-progress

git commit -m "WIP: halfway done"
# BAD: Breaks build for other developers

Output

Provide:

Commit SHA (first 7 chars)
Commit message (full text)
Files committed (list)
Quality gate results (pass/fail)
Next steps (e.g., "Pushed to remote, ready for QA review")

Example Output:

✅ Commit successful

SHA: a3f2c91
Branch: feature/42-seo-foundation

Commit message:
feat(seo): enforce INV-SEO-1 metadata constraints
- Title ≤60 chars
- Description ≤160 chars
Tests: 13 passing
Issue #42

Files committed:
- src/lib/seo/metadata.ts (+45, -12)
- src/lib/seo/__tests__/metadata.test.ts (+67, -5)

Quality gates:
✅ Lint: PASS
✅ Format: PASS
✅ Typecheck: PASS
✅ Tests: PASS (13/13)

Next steps:
✅ Pushed to origin/feature/42-seo-foundation
✅ Issue #42 updated
⏭️  Ready for handoff to backend-engineer

Related Prompts

branch-strategy.prompt.md — Creating and managing branches
create-pr.prompt.md — Creating pull requests
manage-issue.prompt.md — Managing GitHub issues

Version: 1.0.0
Last Updated: 2026-02-25
Owner: operations (git workflows)

# Prompt: Git Commit **Category:** operations **Purpose:** Guide agents to commit code changes properly **Complexity:** Simple **Expected Duration:** 2-5 minutes --- ## Objective Commit code changes to git with proper conventional commit messages, ensuring all quality gates pass before committing. --- ## Context You are an AI agent in a 27-agent engineering organization. Your team uses strict git workflows with conventional commits and quality gates. Every commit must: - Pass local quality gates (lint, typecheck, test) - Use conventional commit message format - Reference the GitHub issue number - Include only related files (≤5 files per commit) --- ## Input Provide: 1. **Files to commit** (absolute paths) 2. **Commit type** (feat, fix, refactor, docs, test, chore, security, perf) 3. **Scope** (seo, cart, checkout, payment, api, ui, etc.) 4. **Subject** (≤72 chars, imperative mood) 5. **Body** (optional, detailed explanation) 6. **Issue number** (e.g., #42) --- ## Execution Steps ### Step 0: Git Context Preflight (MANDATORY) Capture current repository state before making or committing changes: ```powershell git branch --show-current git status --short git log -1 --oneline ``` Include this snapshot in your work notes or issue comment. ### Step 1: Pre-Commit Quality Gates Run these commands and ensure they ALL pass: ```powershell # Hook-equivalent local gate (fast mode) npm run hook:precommit # Optional strict CI-parity gate npm run hook:precommit:ci ``` **If any fail:** Fix issues before proceeding. --- ### Step 2: Stage Files Stage ONLY the files you changed for this specific task: ```powershell git add <file1> <file2> <file3> # Example: git add src/lib/seo/metadata.ts src/lib/seo/__tests__/metadata.test.ts ``` **Verify staged files:** ```powershell git status ``` --- ### Step 3: Craft Commit Message **Format:** ``` <type>(<scope>): <subject> <body (optional)> <footer> ``` **Example 1: Feature commit** ``` feat(seo): enforce INV-SEO-1 metadata length constraints - Title truncated to ≤60 chars - Description truncated to ≤160 chars - Added unit tests for edge cases Tests: 13 passing Coverage: metadata.ts 100% Issue #42 ``` **Example 2: Fix commit** ``` fix(cart): prevent duplicate items in cart state Resolves race condition when user double-clicks "Add to Cart" button. Added debounce logic to addToCart mutation. Fixes #123 ``` **Example 3: Test commit** ``` test(sitemap): add coverage for INV-SEO-3 validation Ensures sitemap includes all 481 active products. Issue #42 ``` --- ### Step 4: Commit ### Step 3.5: Pre-Push Gate (Before `git push`) Run the CI-like pre-push gate: ```powershell npm run hook:prepush ``` Optional strict mode: ```powershell npm run hook:prepush:ci ``` --- ### Step 4: Commit **Short message (≤72 chars total):** ```powershell git commit -m "feat(seo): enforce INV-SEO-1 metadata constraints" ``` **Multi-line message:** ```powershell git commit -m "feat(seo): enforce INV-SEO-1 metadata constraints" -m "- Title ≤60 chars - Description ≤160 chars - Added unit tests Tests: 13 passing Coverage: metadata.ts 100% Issue #42" ``` --- ### Step 5: Push to Remote ```powershell git push origin <branch-name> # Example: git push origin feature/42-seo-foundation # Verify clean checkpoint state git status --short ``` --- ### Step 6: Update GitHub Issue After successful push, add a comment to the GitHub issue: ```powershell gh issue comment 42 --body "Committed metadata helpers (feat: enforce INV-SEO-1). Tests passing." # Preferred detailed format: gh issue comment 42 --body "Checkpoint update:\n\n- Branch: feature/42-seo-foundation\n- Commit: <short-sha>\n- Scope: metadata helpers\n- Checks: lint ✅, typecheck ✅, test ✅\n- Git status: clean\n- Next: proceed to next slice" ``` --- ## Commit Types Reference | Type | Usage | Example | | ---------- | --------------------------------------- | ----------------------------------------- | | `feat` | New feature or enhancement | `feat(seo): add BreadcrumbList schema` | | `fix` | Bug fix | `fix(cart): prevent duplicate items` | | `refactor` | Code restructuring (no behavior change) | `refactor(payment): extract validation` | | `docs` | Documentation changes | `docs(readme): update setup instructions` | | `test` | Adding or updating tests | `test(checkout): add e2e test for flow` | | `chore` | Maintenance (deps, config, etc.) | `chore(deps): update Next.js to 16.1.7` | | `security` | Security improvements/fixes | `security(auth): sanitize user input` | | `perf` | Performance improvements | `perf(api): cache product catalog` | | `style` | Formatting only (no code change) | `style(cart): format with Prettier` | --- ## Common Scopes - `seo` — SEO-related (metadata, sitemap, robots) - `cart` — Shopping cart - `checkout` — Checkout flow - `payment` — Payment processing - `api` — API routes - `ui` — UI components - `store` — State management (Zustand) - `square` — Square API integration - `test` — Test infrastructure - `deps` — Dependencies - `config` — Configuration files --- ## Validation Checklist **Before committing:** - [ ] All quality gates pass (lint, format, typecheck, test) - [ ] Only related files staged (≤5 files) - [ ] Commit message follows conventional format - [ ] Commit message references issue number - [ ] Subject line ≤72 chars - [ ] Subject uses imperative mood ("add" not "added") - [ ] Git context preflight captured (`branch`, `status`, `head`) **After committing:** - [ ] Pushed to remote branch - [ ] GitHub issue commented with update - [ ] Post-push `git status --short` recorded - [ ] No secrets committed (.env, tokens, keys) --- ## Anti-Patterns (DO NOT DO) ### ❌ Committing without running quality gates ```powershell git add . git commit -m "quick fix" # BAD: No quality gates run, might commit broken code ``` ### ❌ Vague commit messages ```powershell git commit -m "updates" git commit -m "misc changes" git commit -m "fix" # BAD: No context, no traceability ``` ### ❌ Committing unrelated files together ```powershell git add src/lib/seo/metadata.ts src/app/api/checkout/route.ts git commit -m "various updates" # BAD: SEO and checkout are unrelated, should be separate commits ``` ### ❌ Committing work-in-progress ```powershell git commit -m "WIP: halfway done" # BAD: Breaks build for other developers ``` --- ## Output Provide: 1. **Commit SHA** (first 7 chars) 2. **Commit message** (full text) 3. **Files committed** (list) 4. **Quality gate results** (pass/fail) 5. **Next steps** (e.g., "Pushed to remote, ready for QA review") **Example Output:** ``` ✅ Commit successful SHA: a3f2c91 Branch: feature/42-seo-foundation Commit message: feat(seo): enforce INV-SEO-1 metadata constraints - Title ≤60 chars - Description ≤160 chars Tests: 13 passing Issue #42 Files committed: - src/lib/seo/metadata.ts (+45, -12) - src/lib/seo/__tests__/metadata.test.ts (+67, -5) Quality gates: ✅ Lint: PASS ✅ Format: PASS ✅ Typecheck: PASS ✅ Tests: PASS (13/13) Next steps: ✅ Pushed to origin/feature/42-seo-foundation ✅ Issue #42 updated ⏭️ Ready for handoff to backend-engineer ``` --- ## Related Prompts - [branch-strategy.prompt.md](branch-strategy.prompt.md) — Creating and managing branches - [create-pr.prompt.md](create-pr.prompt.md) — Creating pull requests - [manage-issue.prompt.md](manage-issue.prompt.md) — Managing GitHub issues --- **Version:** 1.0.0 **Last Updated:** 2026-02-25 **Owner:** operations (git workflows)

{ "prompt": "# Prompt: Git Commit\n\n**Category:** operations \n**Purpose:** Guide agents to commit code changes properly \n**Complexity:** Simple \n**Expected Duration:** 2-5 minutes\n\n---\n\n## Objective\n\nCommit code changes to git with proper conventional commit messages, ensuring all quality gates pass before committing.\n\n---\n\n## Context\n\nYou are an AI agent in a 27-agent engineering organization. Your team uses strict git workflows with conventional commits and quality gates. Every commit must:\n\n- Pass local quality gates (lint, typecheck, test)\n- Use conventional commit message format\n- Reference the GitHub issue number\n- Include only related files (≤5 files per commit)\n\n---\n\n## Input\n\nProvide:\n\n1. **Files to commit** (absolute paths)\n2. **Commit type** (feat, fix, refactor, docs, test, chore, security, perf)\n3. **Scope** (seo, cart, checkout, payment, api, ui, etc.)\n4. **Subject** (≤72 chars, imperative mood)\n5. **Body** (optional, detailed explanation)\n6. **Issue number** (e.g., #42)\n\n---\n\n## Execution Steps\n\n### Step 0: Git Context Preflight (MANDATORY)\n\nCapture current repository state before making or committing changes:\n\n```powershell\ngit branch --show-current\ngit status --short\ngit log -1 --oneline\n```\n\nInclude this snapshot in your work notes or issue comment.\n\n### Step 1: Pre-Commit Quality Gates\n\nRun these commands and ensure they ALL pass:\n\n```powershell\n# Hook-equivalent local gate (fast mode)\nnpm run hook:precommit\n\n# Optional strict CI-parity gate\nnpm run hook:precommit:ci\n```\n\n**If any fail:** Fix issues before proceeding.\n\n---\n\n### Step 2: Stage Files\n\nStage ONLY the files you changed for this specific task:\n\n```powershell\ngit add <file1> <file2> <file3>\n\n# Example:\ngit add src/lib/seo/metadata.ts src/lib/seo/__tests__/metadata.test.ts\n```\n\n**Verify staged files:**\n\n```powershell\ngit status\n```\n\n---\n\n### Step 3: Craft Commit Message\n\n**Format:**\n\n```\n<type>(<scope>): <subject>\n\n<body (optional)>\n\n<footer>\n```\n\n**Example 1: Feature commit**\n\n```\nfeat(seo): enforce INV-SEO-1 metadata length constraints\n\n- Title truncated to ≤60 chars\n- Description truncated to ≤160 chars\n- Added unit tests for edge cases\n\nTests: 13 passing\nCoverage: metadata.ts 100%\n\nIssue #42\n```\n\n**Example 2: Fix commit**\n\n```\nfix(cart): prevent duplicate items in cart state\n\nResolves race condition when user double-clicks \"Add to Cart\" button.\nAdded debounce logic to addToCart mutation.\n\nFixes #123\n```\n\n**Example 3: Test commit**\n\n```\ntest(sitemap): add coverage for INV-SEO-3 validation\n\nEnsures sitemap includes all 481 active products.\n\nIssue #42\n```\n\n---\n\n### Step 4: Commit\n\n### Step 3.5: Pre-Push Gate (Before `git push`)\n\nRun the CI-like pre-push gate:\n\n```powershell\nnpm run hook:prepush\n```\n\nOptional strict mode:\n\n```powershell\nnpm run hook:prepush:ci\n```\n\n---\n\n### Step 4: Commit\n\n**Short message (≤72 chars total):**\n\n```powershell\ngit commit -m \"feat(seo): enforce INV-SEO-1 metadata constraints\"\n```\n\n**Multi-line message:**\n\n```powershell\ngit commit -m \"feat(seo): enforce INV-SEO-1 metadata constraints\" -m \"- Title ≤60 chars\n- Description ≤160 chars\n- Added unit tests\n\nTests: 13 passing\nCoverage: metadata.ts 100%\n\nIssue #42\"\n```\n\n---\n\n### Step 5: Push to Remote\n\n```powershell\ngit push origin <branch-name>\n\n# Example:\ngit push origin feature/42-seo-foundation\n\n# Verify clean checkpoint state\ngit status --short\n```\n\n---\n\n### Step 6: Update GitHub Issue\n\nAfter successful push, add a comment to the GitHub issue:\n\n```powershell\ngh issue comment 42 --body \"Committed metadata helpers (feat: enforce INV-SEO-1). Tests passing.\"\n\n# Preferred detailed format:\ngh issue comment 42 --body \"Checkpoint update:\\n\\n- Branch: feature/42-seo-foundation\\n- Commit: <short-sha>\\n- Scope: metadata helpers\\n- Checks: lint ✅, typecheck ✅, test ✅\\n- Git status: clean\\n- Next: proceed to next slice\"\n```\n\n---\n\n## Commit Types Reference\n\n| Type | Usage | Example |\n| ---------- | --------------------------------------- | ----------------------------------------- |\n| `feat` | New feature or enhancement | `feat(seo): add BreadcrumbList schema` |\n| `fix` | Bug fix | `fix(cart): prevent duplicate items` |\n| `refactor` | Code restructuring (no behavior change) | `refactor(payment): extract validation` |\n| `docs` | Documentation changes | `docs(readme): update setup instructions` |\n| `test` | Adding or updating tests | `test(checkout): add e2e test for flow` |\n| `chore` | Maintenance (deps, config, etc.) | `chore(deps): update Next.js to 16.1.7` |\n| `security` | Security improvements/fixes | `security(auth): sanitize user input` |\n| `perf` | Performance improvements | `perf(api): cache product catalog` |\n| `style` | Formatting only (no code change) | `style(cart): format with Prettier` |\n\n---\n\n## Common Scopes\n\n- `seo` — SEO-related (metadata, sitemap, robots)\n- `cart` — Shopping cart\n- `checkout` — Checkout flow\n- `payment` — Payment processing\n- `api` — API routes\n- `ui` — UI components\n- `store` — State management (Zustand)\n- `square` — Square API integration\n- `test` — Test infrastructure\n- `deps` — Dependencies\n- `config` — Configuration files\n\n---\n\n## Validation Checklist\n\n**Before committing:**\n\n- [ ] All quality gates pass (lint, format, typecheck, test)\n- [ ] Only related files staged (≤5 files)\n- [ ] Commit message follows conventional format\n- [ ] Commit message references issue number\n- [ ] Subject line ≤72 chars\n- [ ] Subject uses imperative mood (\"add\" not \"added\")\n- [ ] Git context preflight captured (`branch`, `status`, `head`)\n\n**After committing:**\n\n- [ ] Pushed to remote branch\n- [ ] GitHub issue commented with update\n- [ ] Post-push `git status --short` recorded\n- [ ] No secrets committed (.env, tokens, keys)\n\n---\n\n## Anti-Patterns (DO NOT DO)\n\n### ❌ Committing without running quality gates\n\n```powershell\ngit add .\ngit commit -m \"quick fix\"\n# BAD: No quality gates run, might commit broken code\n```\n\n### ❌ Vague commit messages\n\n```powershell\ngit commit -m \"updates\"\ngit commit -m \"misc changes\"\ngit commit -m \"fix\"\n# BAD: No context, no traceability\n```\n\n### ❌ Committing unrelated files together\n\n```powershell\ngit add src/lib/seo/metadata.ts src/app/api/checkout/route.ts\ngit commit -m \"various updates\"\n# BAD: SEO and checkout are unrelated, should be separate commits\n```\n\n### ❌ Committing work-in-progress\n\n```powershell\ngit commit -m \"WIP: halfway done\"\n# BAD: Breaks build for other developers\n```\n\n---\n\n## Output\n\nProvide:\n\n1. **Commit SHA** (first 7 chars)\n2. **Commit message** (full text)\n3. **Files committed** (list)\n4. **Quality gate results** (pass/fail)\n5. **Next steps** (e.g., \"Pushed to remote, ready for QA review\")\n\n**Example Output:**\n\n```\n✅ Commit successful\n\nSHA: a3f2c91\nBranch: feature/42-seo-foundation\n\nCommit message:\nfeat(seo): enforce INV-SEO-1 metadata constraints\n- Title ≤60 chars\n- Description ≤160 chars\nTests: 13 passing\nIssue #42\n\nFiles committed:\n- src/lib/seo/metadata.ts (+45, -12)\n- src/lib/seo/__tests__/metadata.test.ts (+67, -5)\n\nQuality gates:\n✅ Lint: PASS\n✅ Format: PASS\n✅ Typecheck: PASS\n✅ Tests: PASS (13/13)\n\nNext steps:\n✅ Pushed to origin/feature/42-seo-foundation\n✅ Issue #42 updated\n⏭️ Ready for handoff to backend-engineer\n```\n\n---\n\n## Related Prompts\n\n- [branch-strategy.prompt.md](branch-strategy.prompt.md) — Creating and managing branches\n- [create-pr.prompt.md](create-pr.prompt.md) — Creating pull requests\n- [manage-issue.prompt.md](manage-issue.prompt.md) — Managing GitHub issues\n\n---\n\n**Version:** 1.0.0 \n**Last Updated:** 2026-02-25 \n**Owner:** operations (git workflows)", "variables": [], "notes": "Commit code changes to git with proper conventional commit messages, ensuring all quality gates pass before committing.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/Coding-Krakken/NeuroLogix", "path": ".github/prompts/operations/git-commit.prompt.md", "ref": "d591fa31ec14afd2cfbb246276ad06b2559c0736", "url": "https://github.com/Coding-Krakken/NeuroLogix/blob/d591fa31ec14afd2cfbb246276ad06b2559c0736/.github/prompts/operations/git-commit.prompt.md", "key": "Coding-Krakken/NeuroLogix/.github/prompts/operations/git-commit.prompt.md" } } }

git-commit

About

Prompt: Git Commit

Objective

Context

Input

Execution Steps

Step 0: Git Context Preflight (MANDATORY)

Step 1: Pre-Commit Quality Gates

Step 2: Stage Files

Step 3: Craft Commit Message

Step 4: Commit

Step 3.5: Pre-Push Gate (Before `git push`)

Step 4: Commit

Step 5: Push to Remote

Step 6: Update GitHub Issue

Commit Types Reference

Common Scopes

Validation Checklist

Anti-Patterns (DO NOT DO)

❌ Committing without running quality gates

❌ Vague commit messages

❌ Committing unrelated files together

❌ Committing work-in-progress

Output

Related Prompts

Use it

Manifest

Reviews

About

Prompt: Git Commit

Objective

Context

Input

Execution Steps

Step 0: Git Context Preflight (MANDATORY)

Step 1: Pre-Commit Quality Gates

Step 2: Stage Files

Step 3: Craft Commit Message

Step 4: Commit

Step 3.5: Pre-Push Gate (Before git push)

Step 4: Commit

Step 5: Push to Remote

Step 6: Update GitHub Issue

Commit Types Reference

Common Scopes

Validation Checklist

Anti-Patterns (DO NOT DO)

❌ Committing without running quality gates

❌ Vague commit messages

❌ Committing unrelated files together

❌ Committing work-in-progress

Output

Related Prompts

Use it

Manifest

Reviews

Step 3.5: Pre-Push Gate (Before `git push`)