commit-message

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. Do not include a section header if there is nothing to put under it.
• Important: Wrap every line of the commit message at 80 characters or fewer, including bullet points.
• Important: Wrap code-like terms in backticks — class/function/variable names, file paths, commands, flags, config keys, and other symbols — so they render as code.
• 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)