菜单
Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Correlate near-in-time events across PR merges, deploys, monitoring (Sentry/NewRelic/Datadog/AppDynamics) and ticket trackers (Jira/Azure DevOps) into confidence-scored clusters that answer "which deploy caused this bug" without manual tab-switching.
A declarative routing engine that turns ticket / error attributes (reporter, label, project, area path, error class, environment) into a tag + AI agent + priority assignment, so cross-source workflows ("security tickets always go to the OWASP reviewer") stay out of code and in user-editable rules.
A paranoid OWASP-Top-10-aware system prompt for AI code review that traces data flow, treats every input as malicious, maps each finding to an OWASP category, and outputs a structured Summary / Findings / Severity / Score block reviewers can act on.
Detect pull requests aging past warn / critical thresholds, score severity, and nudge reviewers via Slack DM, channel, email, or directly as a PR comment — with one-time auto-escalation when a PR hits critical so velocity stops leaking through review queues.
| name | stale-ticket-triage |
| description | Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning. |
| tags | ["project-management","jira","azure-devops","backlog-grooming","ai-agent"] |
| publisher | agena |
Backlogs accumulate dead rows. Most teams have a recurring Friday meeting where someone walks every ticket older than X days and decides whether to close, snooze, or keep it. That hour is the perfect AI workload — the decision is shallow but the volume is high.
Define stale: a ticket is stale when its updated_at is older than
the org's threshold (default 30 days) AND its status is still in the
active set (not Closed / Done / Cancelled).
Schedule the scan (chip-pick: every 6h / 12h / daily 9am / weekly Sundays / monthly). Each run hits the source-platform API for every project the org cares about, lists stale issues, and sends each through a short LLM call.
System prompt the LLM with three explicit verdicts —
close / snooze / keep — plus a one-sentence reason. Be
conservative on close: only pick it when the ticket itself signals
resolution (links a merged PR, mentions a follow-up). Default to
snooze when unsure; never close from silence alone.
Persist each verdict as a triage decision row keyed by
(org, source, external_id) so re-runs are idempotent. Status
transitions: pending → applied / skipped / overridden.
One-click bulk approve in the UI: the human reviews the AI verdicts in a list, hits "Apply all AI suggestions", and the system writes back to Jira / Azure DevOps in a single batch.
VERDICT: close
REASON: Closed by PR #4221 (merged 38 days ago); customer hasn't
responded since the fix shipped.
VERDICT: snooze
REASON: Still relevant but no recent customer activity; revisit when
the related epic resumes.