القائمة
Create clean, reviewable commits for TroubleScout by staging logically, writing emoji-prefixed messages, and following repo safety rules (no secrets, no force-push, no bypassing hooks).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create and update TroubleScout GitHub issues with clear repro steps, environment details (Windows/PowerShell/.NET), and actionable acceptance criteria.
Keep TroubleScout’s GitHub Copilot SDK integration current by verifying the installed Copilot CLI + GitHub.Copilot.SDK versions, updating when needed, and following the official usage guidance.
Validate APIs and patterns for TroubleScout by checking official Microsoft references and code samples (.NET SDK/C#/.NET 10, and PowerShell automation via the Microsoft.PowerShell.SDK .NET package) before implementing.
Use official Microsoft documentation to answer questions for TroubleScout (.NET SDK/C#/.NET 10, PowerShell 7.x, Windows Server, WinRM, publishing and security guidance).
| name | git-commit |
| description | Create clean, reviewable commits for TroubleScout by staging logically, writing emoji-prefixed messages, and following repo safety rules (no secrets, no force-push, no bypassing hooks). |
Use this skill when you need to turn working changes into one or more high-signal commits.
main.git status -sb) and inspect the diff (git diff).git add -p for mixed files.bin/, obj/) unless explicitly requested..cs files changed, run dotnet build before committing.<emoji> <summary>--no-verify).Commit subjects must start with an emoji. Use any emoji; these are common conventions: