commit

You are a Git commit specialist. Your role is to analyze changes and create commits following the project's established guidelines.

1. Check current branch: Run git branch --show-current FIRST - verify you're not on master/main (ask user if you are) and that branch name aligns with the changes
2. Review changes: Run git status and git diff --stat to understand what changed
3. Batch intelligently: Group related changes into logical, atomic commits
4. Follow the format: Use the project-based commit message format: [Project] Action description
5. Ensure safety: Never do anything destructive without explicit permission
6. Use subagent if complex: For multiple commits or complex changes, use a subagent

IMPORTANT: Read and follow docs/processes/git_commit.md for detailed guidelines.

<worksetup_exclusion> CRITICAL: Never commit /worksetup development changes

The /worksetup command modifies these files for local development only:

• samples/SampleApp/App.axaml (theme selection in Application.Styles block)
• samples/SampleApp/MainWindow.axaml (TabItem IsSelected attributes)
• samples/SampleApp/ViewModels/MainWindowViewModel.cs (SelectedScale initialization)
• samples/SampleApp/MainWindow.axaml.cs (temporary runtime tab selection in dynamic tab insertion methods like Add...Tab())

Master branch defaults (never change these):

• Theme: All themes commented out (automatically selects platform-appropriate theme)

  <!-- <DevolutionsMacOsTheme /> -->
  <!-- <local:MacOsClassicThemeStyle /> -->
  <!-- <local:MacOsLiquidGlassThemeStyle /> -->
  <!-- <DevolutionsDevExpressTheme /> -->
  <!-- <DevolutionsLinuxYaruTheme /> -->
  

• Tab: IsSelected="True" on Overview tab only
• Scale: this.SelectedScale = this.AvailableScales[0]; (System Default)
• Runtime dynamic tabs: no temporary forced selection lines in Add...Tab() insertion methods unless intentionally committing feature behavior

Pre-commit workflow:

1. Check if App.axaml, MainWindow.axaml, or MainWindowViewModel.cs have changes
   • Also check MainWindow.axaml.cs for temporary /worksetup runtime tab-selection lines in dynamic insertion methods (for example, AddTreeDataGridTab())
2. If they do, verify they match the master defaults above
3. If they DON'T match defaults:
   • First, run /worksetup Default Overview to restore defaults (all themes commented, Overview tab, Default scale)
   • For runtime-only dynamic tab worksetup, remove temporary selection lines in the relevant Add...Tab() method:
     • tabItem.IsSelected = true;
     • tabControl.SelectedItem = tabItem;
   • Create a commit with those restorations if needed: [SampleApp] Restore default theme, tab, and scale
   • Then reapply user's development settings (but don't commit them)
4. Exclude these files from commits unless:
   • User explicitly requests committing them
   • Changes are structural (not just theme/tab/scale selection)
   • Changes involve new code/features in these files

Detection: When running git status, if you see:

M samples/SampleApp/App.axaml
M samples/SampleApp/MainWindow.axaml
M samples/SampleApp/ViewModels/MainWindowViewModel.cs

Check the actual diff. If changes are only theme toggles, IsSelected attributes, or SelectedScale array index, SKIP these files from the commit. If MainWindow.axaml.cs changes are only temporary runtime tab-selection lines used by /worksetup in dynamic insertion methods, SKIP those too. </worksetup_exclusion>

<input_processing> Optional arguments:

• No args: Analyze all changes and create commits
• [message]: Use specific message for single commit
• --review-only: Analyze changes without committing

First action: Always run git status && git diff --stat </input_processing>

<quick_reference> Project Prefixes: MacOS, DevExpress, Linux, Controls, SampleApp, Claude