Borrowing it
Nothing to install: this file belongs to Devolutions/avalonia-extensions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Devolutions/avalonia-extensions/master/.claude/commands/commit.mdgit clone --depth 1 https://github.com/Devolutions/avalonia-extensionsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/devolutions/avalonia-extensions/commit)<a href="https://agentmods.dev/commands/devolutions/avalonia-extensions/commit"><img src="https://agentmods.dev/badge/commands/devolutions/avalonia-extensions/commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/devolutions/avalonia-extensions/commit"><img src="https://agentmods.dev/badge/commands/devolutions/avalonia-extensions/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00009 | $0.01137 |
| Opus 5.5 | $0.00004 | $0.00455 |
| Sonnet 5.5 | $0.00002 | $0.00227 |
| Haiku 4.5 | $0.00001 | $0.00114 |
Grade A, and why
commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Git commit specialist. Your role is to analyze changes and create commits following the project's established guidelines.
- Check current branch: Run
git branch --show-currentFIRST - verify you're not on master/main (ask user if you are) and that branch name aligns with the changes - Review changes: Run
git statusandgit diff --statto understand what changed - Batch intelligently: Group related changes into logical, atomic commits
- Follow the format: Use the project-based commit message format:
[Project] Action description - Ensure safety: Never do anything destructive without explicit permission
- 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 likeAdd...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:
- Check if App.axaml, MainWindow.axaml, or MainWindowViewModel.cs have changes
- Also check
MainWindow.axaml.csfor temporary/worksetupruntime tab-selection lines in dynamic insertion methods (for example,AddTreeDataGridTab())
- Also check
- If they do, verify they match the master defaults above
- If they DON'T match defaults:
- First, run
/worksetup Default Overviewto 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)
- First, run
- 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
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 110 lines · 9 tokens per session scan A b27e7a49ac1b
commit is a command published in the GitHub repository Devolutions/avalonia-extensions (84 stars, last pushed 15d ago), licensed MIT. It adds 9 tokens to every session and 1,137 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.