prepare-commit

Prepare the current working tree changes for commit by delegating to the `git-committer` agent. ## Delegation Use the Task tool to launch the `git-committer` agent (subagent_type). Pass the full context of what needs to be done. ## Steps 1. Run `dotnet format` on changed files 2. Run `dotnet build` to verify compilation 3. Run `dotnet test` to verify all tests pass 4. If files were added/removed/renamed in `src/`, update `.claude/reference/file-organization.md` and `.claude/reference/architecture.md` 5. Update relevant README.md files if features or APIs changed 6. Stage relevant files with `git add` (specific files, not `-A`) 7. Generate a conventional commit message based on the staged changes ## Rules - **NEVER** execute `git commit` — the user reviews and commits manually - **NEVER** push to remote - Use specific file paths with `git add`, never `git add -A` or `git add .` - Skip files that likely contain secrets (`.env`, credentials) - Follow the repository's existing commit message style (check `git log`) - Use conventional commits if you can infer the type (feat, fix, docs, etc.) from the changes and you think it would be helpful for the user to see that in the message. Note that conventional commits will be added to the release notes by the generate-changelog.yml workflow, so they should be used when the commit represents a meaningful change that should be highlighted in the changelog. However, if the changes are minor or don't fit well into a conventional commit type, it's better to write a clear, descriptive message without forcing a conventional format. --- > Source: [cmdscale/CmdScale.EntityFrameworkCore.TimescaleDB](https://github.com/cmdscale/CmdScale.EntityFrameworkCore.TimescaleDB) — distributed by [TomeVault](https://tomevault.io). <!-- tomevault:4.0:skill_md:2026-07-19 -->