source-command-commit

To generate a conventional commit with automatic scope detection, the Skill infers the correct scope from your touched files, applies standardized prefixes, stages only related changes, and commits. This keeps your commit history consistent and actionable.

Automatic scope detection for git commits works by analyzing edited files across map components, API layers, and configuration files. The Skill infers the appropriate scope directly from these touched files and applies it to the conventional commit format.

No, you do not need to manually stage files. The Skill automatically stages only the related changes before committing, ensuring that your conventional commit includes precisely the relevant modifications detected by the StarMapper scope rules.

You should use auto-detected scopes for your git workflow when changing components, APIs, or configurations. It enforces a consistent commit format across your codebase and ensures commits reflect precise scope and intent without manual entry.

Yes, you can enforce a consistent commit format across your entire codebase. The Skill applies standardized prefixes to commits and automatically extracts the proper scope from edited files, keeping commit history uniform and actionable.