Generate a single, compliant Conventional Commit message based on a provided Git diff/patch output snippet.
Act as an expert Git engineer strictly adhering to the Conventional Commits specification. Analyze the input Git diff/patch. Determine the commitment type ('fix' for bugs, 'feat' for new features, 'refactor' otherwise). Output ONLY the complete commit line—subject, body, and scope tag—in conventional format.
[PASTE DIFF/PATCH HERE]
Condense PR Description into Single Commit
Transform a detailed Pull Request description into one concise, formal Conventional Commit message.
Review the following Pull Request summary. Synthesize the core change into one standard Conventional Commit. Select the most precise type (e.g., feat, chore) and derive the scope from the primary affected module. Output only the resulting commit line.
PR Summary:...
Validate & Suggest Type/Scope
Analyze a high-level change description and suggest the most appropriate Conventional Commit type and narrow scope term.
Based on the detailed description of recent code changes, suggest the most suitable Conventional Commit type (e.g., feat, fix, chore, refactor) and recommend a specific scope label if applicable. Output only the suggested categorization, formatted as: TYPE(scope).
Change Details: [DESCRIBE CHANGES HERE]
Force Breaking Change Footer Generation
Draft a conventional commit that explicitly includes the required 'BREAKING CHANGE' footer detailing backward incompatibility.
Generate a Mandatory Conventional Commit message that signifies a breaking change. The type must be 'BREAKING' or explicitly include 'BREAKING CHANGE:' in the footer. The subject must summarize the breaking change, and the body must clearly explain the necessary migration steps for consumers.
Generate Refactor Commit for Internal Polish
Create a precise `refactor` commit message focused on improving code structure, performance, or readability without changing observable behavior.
I completed a significant internal refactoring of the token decoding logic to use async/await patterns, enhancing performance metrics slightly. Write a Conventional Commit message. Type: 'refactor'. Scope: 'tokens'.
Standardize Dependency Version Bump Commit
Format updates to dependencies, tools, or boilerplate into a clean `chore` commit.
Draft a standard 'chore' type conventional commit message documenting the required update of the TypeScript compiler from 5.3.3 to 5.4.0. The scope should be 'typing'.
Commit for E2E or Unit Test Coverage
Generate a `test` type commit message exclusively for developing, updating, or fixing automated tests.
I integrated functional end-to-end tests for the new subscription management flow using Playwright. Construct the Conventional Commit message. Type: 'test'. Scope: 'e2e-subscriptions'.
Commit for Specification Documentation Changes
Create a `docs` commit message specifically for updating API specifications, OpenAPI files, or JSDoc outside of general README updates.
Update the OpenAPI specification file to reflect the new optional parameter added to the /metrics endpoint definition. Generate a concise 'docs' conventional commit message. Scope: 'api-spec'.
Draft Style Commit for Formatting Pass
Draft a `style` commit message used when only cosmetic changes enforced by linters (no logic change) are committed.
I executed ESLint fixer across all JavaScript modules, adjusting spacing and line endings uniformly. Generate a 'style' conventional commit message. Scope: 'linting'.
Precise Fix for Runtime Error
Generate a 'fix' commit detailing the resolution of a specific runtime error or null pointer issue in a core service.
Generate a conventional commit message. Type: 'fix'. Scope: 'user-service'. The fix addresses an intermittent race condition causing user creation to fail if database connection latency spikes above 200ms. Detail the synchronization mechanism added.
New REST Endpoint Implementation Commit
Draft a 'feat' commit clearly documenting the implementation of a new REST API method.
We finalized and deployed the POST endpoint `/v1/billing/process_refund`. Generate a 'feat' conventional commit message. Scope: 'billing-api'. The body must confirm transactional integrity was maintained.
Generate Standardized Revert Message
Create the official Conventional Commit format message when reverting a previously merged commit, including the original hash.
I must revert commit hash XYZ987654 because it introduced memory leaks under high load. Construct the official Conventional Commit revert message, including a summary of the issue encountered during verification.
Commit High-Impact Performance Optimization
Generate a 'perf' commit message after implementing a significant performance boost identified via profiling.
After profiling the internal caching layer, I implemented an LRU eviction strategy, resulting in a 45% reduction in memory pressure. Generate a 'perf' type conventional commit message. Scope: 'caching'.
Build System Configuration Adjustment
Standardize commits related to updating CI/CD pipelines or build tool version constraints using the 'build' type.
The Github Actions workflow configuration was modified to use a newer Node.js runner version (20.x) for security compliance. Generate a conventional commit message. Type: 'build'. Scope: 'ci'.
Feature Flag Related DB Migration
Generate a commit message for necessary database changes that support a new feature flag rollout.
Create a conventional commit message for running a migration that adds the necessary structural metadata columns to support the upcoming 'dark-mode' feature flag rollout. Type: 'feat'. Scope: 'database-schema'.
Critical Security Patch Resolution Commit
Draft a high-priority 'fix' commit specifically detailing the resolution of a known security flaw.
A CVE related to insecure deserialization in the GraphQL resolver was patched. Generate a conventional commit message. Type: 'fix'. Scope: 'security'. Explicitly mention the patch source (e.g., lib update).
Language Fallback Implementation in i18n
Generate a commit for changes related to internationalization handling, such as default language fallbacks.
Implemented logic ensuring that if a requested translation key is missing in the primary locale (EN), it correctly falls back to the base fallback language definition. Generate a conventional commit message. Type: 'feat'. Scope: 'i18n'.
Audit & Update of Core Dependency Line
Handle substantial version upgrades impacting core architecture, categorized as 'chore' when stability is prioritized over new feature delivery.
We performed an audit and upgraded core utility library Zod from v3 to v4. This necessitated several minor signature adjustments across affected modules. Generate a 'chore' type conventional commit message. Scope: 'libraries'.
First Commit for New Repository Structure
Create the necessary initial commit message for setting up a brand new Git repository boilerplate.
This commit initializes the repository including Docker setup files, standard configuration files (.gitignore, package.json), and the initial README structure based on the established template. Generate the Conventional Commit message. Type: 'chore'. Scope: 'init'.
Implement New Caching Strategy in API
Draft a 'feat' commit documenting the introduction of a new mechanism like Redis caching on specific GET requests.
Implemented a shared Redis caching layer, resulting in a 70% reduction in latency for the /users/list endpoint. Generate a 'feat' conventional commit message. Scope: 'caching'.
Aggressive Dead Code Removal Commit
Generates a commit specifically for permanently removing large, verified obsolete code modules.
Removed the defunct V1 payment processing module and all associated legacy endpoint handlers, as confirmed deprecated for three releases. Write a Conventional Commit message classifying this cleanup. Type: 'chore'. Scope: 'cleanup'.
Modification of CI/CD Infrastructure Files
Generate a commit for updating infrastructure-as-code files (Terraform, Ansible, Dockerfiles).
The main Dockerfile was modified to install a necessary runtime dependency (libssl-dev) during the build stage. Generate a conventional commit message. Type: 'build'. Scope: 'dockerfile'.
Integrate Formatting Hook into Git Flow
Create a commit message specifically for integrating or configuring code quality enforcement via Git hooks.
Configured Husky to run `npm run lint` before every commit attempt to prevent formatting errors from reaching the repository. Conventional Commit message required. Type: 'chore'. Scope: 'git-hooks'.
Fixing Flaky End-to-End Test Case
Draft a commit message addressing instability or incorrect assertions in E2E tests.
Root-caused and fixed a flaky test in the checkout pipeline that timed out intermittently due to incorrect explicit waits being used. Generate a 'test' conventional commit message. Scope: 'e2e-checkout'.
Adding Clarifying Inline Comments/JSDoc
Generate a 'docs' commit when only adding clarifying internal documentation elements like comments or JSDocs.
Reviewed the critical calculation function `calculateTax()` and added detailed inline comments explaining the specific tax law references used in lines 45-52. Generate a 'docs' conventional commit message. Scope: 'code-comments'.
Turn these prompts into a reusable workspace
Save your favourite prompts once, reuse them with Alt+P, keep a live Table of Contents of long chats, and export conversations when you're done.
