// Commit session changes to git. Identify files from session context, ask user pick message, run validation only if needed. Use when user want commit / save / land changes.
Query the local Postgres database of the active Aspire worktree via psql.
Apply a downstream brand to a PlatformPlatform fork. Edits one config file, drops in eight supplied logo assets, renames the solution and CLI to the new brand, and rotates UserSecretsId across every csproj. Skips all other source files. Use once per downstream fork after cloning, or to re-flip a brand later.
Stop the .NET Aspire AppHost and its Docker containers via the developer CLI. Defaults to the current worktree; supports stopping all worktrees or a specific base port.
Create a GitHub pull request.
Trigger only on explicit "ultra review" or "ultra-review".
Lint code via the developer CLI - backend (.NET via JetBrains inspectcode), frontend (oxlint), and the developer CLI itself.
| name | commit |
| description | Commit session changes to git. Identify files from session context, ask user pick message, run validation only if needed. Use when user want commit / save / land changes. |
Asked commit now != permission for future commits. Each commit needs explicit user instruction. No amend, revert, push without explicit ask.
Speed critical. No slow commands unless changes warrant.
git status / log / diff.Frontend changes touching user-facing strings: inspect .po files for missing translations and translate them. Missing keys: flag user; don't commit until resolved.
Skip if build / test / lint / format / aspire-restart / e2e already ran clean this session on same files. No re-run, no offer.
When need:
Run build first:
build (no flags - covers backend AND frontend; backend can break frontend via API contracts)build --frontendbuild --cliAfter build, parallel (--no-build where applicable):
format --<target>, lint --<target> - per target whose code changedtest --no-build - backend changeaspire-restart - service / Aspire wiring change (large only)e2e - large frontend or shared E2E-covered change; --smoke for low-impact (rare pre-commit)Judge target by file (project / manifest / lock files affect owning build, even when extension non-obvious).
Simple, focused commit: propose one message, commit.
Complex (multiple unrelated changes, doesn't fit one line, validation choices needed, file set ambiguous): use AskUserQuestion - 2-4 message options + conditionals in one call. No back-and-forth. Follow up only on "Other" or unexpected input.
No conventional commit prefixes (feat:, fix:, docs:, chore:).
Conditional questions:
Stage explicit files. Never git add -A or git add ..
Asked commit now != permission for future commits.