القائمة
Generate conventional commit messages from staged git changes when the task is to name or format a commit, not to review code or write release notes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run Microsoft SkillOpt experiments for agent skills, prompts, or instruction files with clean train/validation/held-out splits, adapter setup, bounded rollouts, artifact collection, and honest reporting. Use when the user wants to use SkillOpt, optimize a skill with SkillOpt, benchmark prompt variants, run multi-epoch skill optimization, check held-out quality, or diagnose SkillOpt runs.
Run pre-implementation AI consulting engagements—company research, discovery, maturity assessment, opportunity prioritization, and proposal/SOW/roadmap creation—and use only for advisory work, not implementation.
Guide annuity and life-insurance sales workflows—discovery, suitability, product selection, objections, closing, and servicing—when supporting licensed insurance sales conversations or deliverables.
Generate API reference documentation from source code—endpoints, schemas, auth, errors, and examples—when the task is to document an existing API rather than design or implement one.
Turns an approved build spec into a minimal technical implementation plan, including system components, human-in-the-loop boundaries, workflows, and delivery milestones. Use when an internal automation, concierge workflow, or lightweight product has already been chosen and now needs a concrete build plan.
Generate release notes and changelogs from git history with SemVer classification, grouped changes, and migration notes when documenting what changed between versions or refs.
| name | git-conventional-commits |
| description | Generate conventional commit messages from staged git changes when the task is to name or format a commit, not to review code or write release notes. |
Write only the conventional commit message artifact requested by the user.
Rules:
<type>(<scope>)!: <description> for breaking changes, otherwise <type>(<scope>): <description>.feat, fix, refactor, docs, test, ci, build, perf, or chore.! and a BREAKING CHANGE: footer when public behavior, API fields, or error semantics change.