Commit

Smart Commit

Create a validated commit with proper service-scoped message format. Optional argument: $ARGUMENTS (commit message override).

Step 1: Detect Changed Files

# Staged changes
git diff --cached --name-only

# Unstaged changes (for reference)
git diff --name-only

# Untracked files
git ls-files --others --exclude-standard

If nothing is staged, show the user what's unstaged/untracked and ask what to stage.

Step 2: Map Changes to Services

Map every changed file to its service:

Step 3: Run Validation for Each Affected Service

For each affected service, run its validation command. Report results as a table:

| Service | Validation | Status |
|---------|-----------|--------|
| api-server | make validate | PASS/FAIL |

If any validation fails:

• Show the error output
• Ask the user: "Validation failed for {service}. Fix issues and retry, or commit anyway?"
• Do NOT proceed with commit unless user explicitly says to skip validation

Step 4: Generate Commit Message

If $ARGUMENTS is provided, use it as the commit subject but still prepend the semantic type and scope.

Format: type(scope): subject (per .github/semantic.yml)

Allowed types:

Allowed scopes (required):

Rules:

• Single scope: fix(ui): handle null pointer in settings page
• Ticket number scope: feat(NB-1234): add Azure onboarding flow
• Scope is required — if no dedicated scope matches, use a ticket number NB-xxx or nb-xxx

If no $ARGUMENTS, analyze the diff to generate an appropriate message. Present the proposed message to the user for confirmation before committing.

Step 5: Stage and Commit

Stage files if not already staged (ask user first if there are unstaged changes to include):

git add <specific files>

Commit:

git commit -m "type(scope): subject"

NEVER use git add -A or git add . — always add specific files.

Step 6: Output Summary

Committed: type(scope): subject
  {N} files changed, {A} insertions(+), {D} deletions(-)
  Services: {list}
  Validation: all passed