القائمة
Provides issue triage workflow, priority definitions, and report format. Use when analyzing GitHub issues and PRs, assessing priority, or generating triage reports.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Provides deployment commands and troubleshooting for Azure Container Apps. Use when running azd commands, deploying containers, debugging deployment failures, or updating infrastructure in this repository.
Provides SSE streaming patterns for the chat API and frontend. Use when implementing or modifying chat streaming, handling SSE events, or troubleshooting message flow between frontend and backend.
Provides research patterns for Foundry Agent Service SDK. Use when implementing agent features, looking up SDK methods, finding code samples, or troubleshooting Azure.AI.Projects API usage.
Provides architecture overview with state machines, SSE event flow, and file mappings. Use when understanding system design, debugging state issues, or maintaining ARCHITECTURE-FLOW.md.
Provides C# and ASP.NET Core coding standards for this repository. Use when writing or modifying C# code, implementing API endpoints, configuring middleware, or working with authentication in the backend.
Diagnose and fix incomplete local development setup. Use when dev servers fail to start, env vars are missing, authentication errors occur, or before running any dev commands for the first time.
| name | triaging-issues |
| description | Provides issue triage workflow, priority definitions, and report format. Use when analyzing GitHub issues and PRs, assessing priority, or generating triage reports. |
Gather open issues and PRs, analyze them, and recommend next steps. Search the codebase to identify affected components — don't rely on hardcoded file mappings.
| Priority | Criteria |
|---|---|
| 🔴 Critical | Production broken, security issue, data loss |
| 🟠 High | Major feature broken, blocking users |
| 🟡 Medium | Feature degraded, workaround exists |
| 🟢 Low | Minor issue, cosmetic, nice-to-have |
| Size | Estimate |
|---|---|
| S | Hours |
| M | 1-2 days |
| L | 3-5 days |
| XL | 1+ week |
| Prefix | Values |
|---|---|
area: | backend, frontend, auth, streaming, infra, docs |
type: | bug, feature, enhancement, chore, docs |
priority: | critical, high, medium, low |
| # | Title | Priority | Type | Complexity |
|---|
| # | Title | Author | Status | Files Changed |
|---|
# List open issues
gh issue list --state open
# Search for potential duplicates
gh issue list --search "keyword"
# View issue details
gh issue view <number>
# List open PRs
gh pr list --state open
# View PR details and diff
gh pr view <number>
gh pr diff <number>
Before deep-diving into an issue, search for duplicates:
gh issue list --search "<keywords>" with key terms from the issue title and body.gh issue list --state closed --search "<keywords>".gh issue edit, gh issue close, gh issue labelgh pr merge, gh pr close, gh pr review --approvelist, view, search, diff