commit-message

name	commit-message
description	Draft a structured commit message for all uncommitted changes, auto-detecting project type (React, Rails, or generic).
disable-model-invocation	true

Commit message draft

Draft a commit message for all the uncommitted changes.

CRITICAL: MANDATORY FIRST STEP

YOU MUST run git diff HEAD as your FIRST action before doing anything else.

DO NOT attempt to infer changes from context or memory. DO NOT skip this step. DO NOT proceed without running this command first.

Process

1. FIRST: Run git diff HEAD in the terminal to get ALL uncommitted changes
2. SECOND: Analyze the diff output to understand what changed
3. THIRD: Detect the project type from the files in the diff
4. FOURTH: Generate the commit message using the appropriate template

Instructions:

• If I specify "React" or "Rails", use the corresponding template below
• If I don't specify a project type, try to infer it from the file extensions and structure:
  • React: Look for .jsx, .tsx files, component folders, package.json with React dependencies
  • Rails: Look for .rb files, controllers/, models/, db/migrate/ folders, Gemfile
• If the project type cannot be determined, provide a generic commit message with a clear description of changes
• Important: Omit any template sections that don't have relevant changes
• Important: Output the commit message within a fenced code block. You should use four backticks (````) for the outer code block, so that any code blocks withing will render correctly.

---

React Template

(feat|fix|chore): (Brief title of change)

(Brief description of the change)

Components Changes:
- (Any Components changes)

API Integration:
- (Any changes to the API integration)

UI/UX Features:
- (Any changes to the UI/UX Features)

Testing:
- (Any testing updates)

Other Changes:
- (Any other changes)

---

Rails Template

(feat|fix|chore): (Brief title of change)

(Brief description of the change)

Database Changes:
- (Any database/migration changes)

API Changes:
- (Any overall API updates)

Controller Changes:
- (Any controller updates)

Model Changes:
- (Any model updates)

Testing:
- (Any testing updates)

Other Changes:
- (Any other changes)

Request Body Changes:
(If any API endpoints were added or modified that accept request bodies, include the full request structure)

Example Request Body:
```json
(Full JSON request body structure with required/optional fields)
```

Response Body Changes:
(If API response bodies changed, include the full response structure for both success and error cases)

Success Response:
```json
(Full JSON response body for successful requests)
```

Error Response(s):
```json
(Full JSON response body for error cases)
```

---

Generic Template (when project type is unclear)

(feat|fix|chore): (Brief title of change)

(Brief description of the change)

Changes:
- (List key changes by file or functionality)

Impact:
- (Any notable impacts or side effects)