OpenParable
Skip to content
← Back to skills

Issue Triage To Teams

Productivity
issue-triage-to-teams

Issue Triage To Teams is an Agent Skill for productivity published in the Azure-Samples/get-started-with-ai-chat repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Triage new GitHub issues by summarizing, classifying, proposing labels/assignees, and producing a Teams-ready notification message.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Azure-Samples/get-started-with-ai-chat/blob/HEAD/.github/skills/issue-triage-to-teams/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/issue-triage-to-teams, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Issue Triage → Teams Notification Skill

Purpose

When a new GitHub issue is created, produce:

  1. A short summary (1–3 bullets)
  2. A classification: bug / feature / question / docs
  3. Suggested labels (2–6)
  4. A Teams-ready message body (short, scannable), including a deep link to the issue

This skill is designed to be used with GitHub issues in this repository and to generate consistent, high-signal notifications.

Inputs (what you should look for)

  • Issue title
  • Issue body
  • Issue author
  • Issue URL
  • Existing labels (if any)
  • Repository context (README / contributing guidelines if needed)

Workflow

  1. Read the issue: title + body.
  2. Summarize in 1–3 bullets. Keep it factual; do not invent details.
  3. Classify as one of:
    • bug (unexpected behavior, regression, crash, incorrect output)
    • feature (new capability request)
    • question (how-to, clarification, usage)
    • docs (documentation improvements)
  4. Propose labels:
    • Always include one of: type:bug, type:feature, type:question, type:docs
    • Add area:* labels if the issue mentions a component
    • Add priority:* only if clearly implied (e.g., production down)
  5. Propose next action:
    • What info is missing? (logs, repro steps, expected/actual)
    • Suggest a first investigation step
  6. Generate Teams message (final output) using this template:

Teams Message Template

New Issue: #{ISSUE_NUMBER} {ISSUE_TITLE}
Repo: {REPO} | Author: {AUTHOR} | Type: {CLASSIFICATION}
Summary:

  • {BULLET_1}
  • {BULLET_2}
  • {BULLET_3 (optional)}

Suggested labels: {LABELS_COMMA_SEPARATED}
Next step: {ONE_SENTENCE_NEXT_STEP}
Link: {ISSUE_URL}

Guardrails

  • Don’t guess. If info is missing, say so.
  • Keep output short enough to fit within webhook message limits.
  • Prefer neutral, actionable language.