メニュー
Stage, commit, and (optionally) push the current changes on the CURRENT branch, following project governance. Use ONLY when Dan explicitly asks to commit and/or push.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Add a domain entity, aggregate, or value object to the .NET API — rich mutable class with private ctor + static factory (UUIDv7), invariants that throw, tenant_id, identity equality; records for value objects. Use when modeling new domain state under apps/api/{{ProjectName}}.Domain.
Add a Minimal API endpoint (a feature/use case) to the .NET API — feature folder, IEndpoint self-registration, contract validation, Kommand dispatch, Result→ProblemDetails. Use when adding or changing an HTTP endpoint under apps/api/{{ProjectName}}.Api.
Author a CQRS command or query in the {{ProductName}} backend using the Kommand library, the three-scope validation model, and the Result<T> failure pattern. Use whenever creating or modifying a command/query/handler/validator in apps/api/{{ProjectName}}.Application, or wiring its endpoint in {{ProjectName}}.Api.
Choose and wire AI features in the .NET backend — LLM calls, agentic tool-calling/multi-step workflows, RAG/vector search, structured output, streaming. Use when adding or changing anything that talks to a model or orchestrates agents (your agentic pipeline). Tailored to our LLM provider + MAF + pgvector stack.
Scan .NET/C# code for performance anti-patterns (async, memory/strings, collections/LINQ, regex, serialization, I/O) with tiered severity, reporting findings without editing. Use when auditing hot paths, reviewing allocation-heavy code, or analyzing the API for optimization opportunities.
Add or change EF Core (Npgsql/PostgreSQL) persistence in the .NET backend — entities, EF configurations, repositories, queries, migrations. Use when adding a table/entity, a query, a repository, or a migration under apps/api.
| name | push |
| description | Stage, commit, and (optionally) push the current changes on the CURRENT branch, following project governance. Use ONLY when Dan explicitly asks to commit and/or push. |
| argument-hint | ["commit message hint"] |
| disable-model-invocation | true |
| allowed-tools | Read, Bash |
Per CLAUDE.md, git mutations happen only when Dan explicitly asks, per action — git add / commit /
push each trigger a confirmation prompt (the protect-commands hook). Approval for one step never implies another.
No SDLC assumptions. Work happens on whatever branch Dan is on. "Push" means push the current branch to its remote — do NOT create branches, switch branches, open PRs, or assume any branching model or process.
git status, git diff, git log -5 --oneline (match the existing commit style), and note the
current branch (git rev-parse --abbrev-ref HEAD)..env, secrets, or credentials; confirm none are in the diff.git add -A unless told otherwise.Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Never use --no-verify or skip hooks; never force-push or rewrite shared history.git push). If it
has no upstream, set it for the current branch (git push -u origin <current-branch>) — never switch to or
create a different branch.Report exactly what you staged, the commit SHA, the branch, and whether you pushed.