メニュー
Generates a Conventional Commits-style English commit message by analyzing staged git changes. Use when the user asks for a commit message, wants to commit changes, mentions "commit", "git commit", or asks for help writing a commit message.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when adding query parameter filters to a monitor list endpoint. Covers the 3-class pattern (FilterInput / FilterDescriptor / Filter), bracket-notation binding with [eq]/[contains] operators, conflict validation, type-discriminated 400 validation, and in-memory LINQ apply — all derived from the component filter implementation.
Scope is repo-wide domain knowledge (not bound to a single workspace). vNext Runtime platform referansı. Workflow, state, transition, task, schema, view, function ve extension kavramlarını, JSON tanım yapılarını ve C# mapping/rule pattern'lerini kapsar. vNext bileşenleri oluşturulurken veya düzenlenirken bu skill'i kullanın. Trigger this skill whenever vNext workflow/task/schema/view/function/extension JSON or `.csx` mapping/rule files are being created or edited anywhere in the monorepo (or in target vnext domain repositories).
Creates a structured English GitHub issue using gh CLI based on a user-provided scope description. Translates the scope to English, optionally scans the codebase to enrich the technical description, shows the draft for user approval, then opens the issue. Use when the user asks to open an issue, create a GitHub issue, report a bug/task/feature, or says "issue aç", "issue oluştur", or "scan project" / "projeyi tara".
Creates an English GitHub Pull Request using gh CLI by analyzing commits on the current branch compared to the base branch. Generates a structured PR title and body, shows it for user approval, then creates the PR. Use when the user asks to create a PR, open a pull request, push and create PR, or mentions "gh pr", "pull request", or "open PR".
Generate or update vNext platform documentation for the vnext-docs Docusaurus site. Use when the user says "döküman oluştur", "create docs", "document this feature", or asks to update/sync documentation after a code change.
Generates a comprehensive matrix report from vnext-meta JSON files. Outputs a markdown table showing features, deprecations, known issues, components, and limits by version. Use when the user says "meta matrix", "meta rapor", "feature matrix", "meta ozet", or "meta tablo".
| name | git-commit-message |
| description | Generates a Conventional Commits-style English commit message by analyzing staged git changes. Use when the user asks for a commit message, wants to commit changes, mentions "commit", "git commit", or asks for help writing a commit message. |
git diff --cached to inspect staged changes.git add first.<type>(<scope>): <short subject>
<optional body>
<optional footer>
<scope> is optional; use the affected module, layer, or file area| Type | Use when |
|---|---|
feat | New feature or capability |
fix | Bug fix |
refactor | Code restructuring without behavior change |
perf | Performance improvement |
test | Adding or updating tests |
docs | Documentation only |
chore | Build scripts, tooling, dependencies, config |
ci | CI/CD pipeline changes |
style | Formatting, whitespace (no logic change) |
revert | Reverting a previous commit |
BREAKING CHANGE: <description> for breaking changesCloses #<issue> for linked issuesSimple feature:
feat(auth): add JWT refresh token support
Bug fix with body:
fix(repository): prevent duplicate inserts on concurrent requests
EF Core change tracking was not reset between retries, causing
duplicate key violations under high concurrency. Reset tracker
after each failed attempt.
Chore:
chore(deps): upgrade EF Core to 9.0.4
Breaking change:
feat(api)!: remove deprecated v1 endpoints
BREAKING CHANGE: /api/v1/* routes are no longer available.
Migrate to /api/v2/*.
Present the commit message in a fenced code block so the user can copy it easily:
git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body if any>
EOF
)"
If the diff contains multiple unrelated concerns, suggest splitting into separate commits and offer a message for each.