commit

Core Guidelines

/key-guidelines

Dependencies

• use git-operations-specialist skill

Instructions

Required Execution Items

1. Check Staging Status: Run

   git status

   to confirm what changes are staged
2. Review Staged Changes: Use

   git diff --staged

   to review the content of staged changes
3. Create Commit: Commit the staged changes with an appropriate commit message
4. Verify Commit: Run

   git status

   after committing to confirm the commit was successful

Commit Message Guidelines

• Follow the

  .gitmessage

  template format
• Use appropriate commit type prefixes:

  feat

  ,

  fix

  ,

  refactor

  ,

  docs

  ,

  style

  ,

  test

  ,

  chore

• Write clear, concise messages that describe the change

⚠️ Important Constraints

• Never use any

  git add

  commands – Only commit what is already staged
• Use HEREDOC – Maintain proper formatting of commit messages
• Stage verification first – Always check what's staged before committing
• Single commit – Create one commit for all currently staged changes

Example Usage

# Staged files:
- apps/api/src/routes/timeline.ts
- apps/api/src/types/timeline.ts

feat: タイムラインAPIのルートと型定義を追加