AgentSkillsCN

gh-dify-daily-triage

每日使用 gh CLI 对 langgenius/dify、langgenius/dify-plugins、langgenius/dify-official-plugins、langgenius/webapp-conversation、langgenius/webapp-text-generator、langgenius/dify-docs 以及 langgenius/dify-plugin-daemon 进行议题与拉取请求的分类整理。当您被要求列出当天创建且仍处于开放状态的议题与 PR（非草稿 PR），并判断每个议题是否关联了 PR，或每个 PR 是否关联了议题；同时以 Markdown 表格的形式呈现结果，去除作者与状态列，仅保留可点击的 URL，并附上详尽的注意力分析时，此技能将助您高效完成任务。

SKILL.md
--- frontmatter
name: gh-dify-daily-triage
description: Daily GitHub triage for langgenius/dify, langgenius/dify-plugins, langgenius/dify-official-plugins, langgenius/webapp-conversation, langgenius/webapp-text-generator, langgenius/dify-docs, and langgenius/dify-plugin-daemon using the gh CLI. Use when asked to list issues and PRs created today that are open (non-draft PRs), show whether each issue has a linked PR or each PR has a linked issue, format results as Markdown tables without author/state columns and with clickable URLs, and provide attention analysis.

GH Dify Daily Triage

Overview

Generate a daily triage report for Dify GitHub repos with open issues and open non-draft PRs created today, formatted as Markdown tables plus a short attention analysis.

Workflow

  1. •Run the data script to fetch issues and PRs created today.
  2. •Verify filters: issues must be open; PRs must be open and draft:false.
  3. •Present tables per repo (Issues, PRs). Do not include author or state columns. URLs must be clickable Markdown links.
  4. •Add an Attention section highlighting what needs action.

Run The Script

Use the bundled script to fetch and format data.

bash
python /Users/minibanana/.codex/skills/gh-dify-daily-triage/scripts/dify_daily_triage.py

Optional flags:

  • •--date YYYY-MM-DD to override “today”.
  • •--repos owner/repo ... to override the repo list.
  • •--no-proxy if gh fails due to local proxy settings.

Example:

bash
python /Users/minibanana/.codex/skills/gh-dify-daily-triage/scripts/dify_daily_triage.py --date 2026-02-05

Output Format Rules

  • •Produce sections per repo: ## repo, then ### Issues and ### PRs.
  • •Table columns (no author/state columns): Type, #, Title, Labels, Link, Created (UTC), URL.
  • •URL column must be clickable, e.g. [link](https://github.com/...).
  • •Link column labels:
    • •Issues: linked-pr: [#123](...) or no-linked-pr.
    • •PRs: linked-issue: [#123](...) or no-linked-issue.

Attention Analysis Heuristics

Call out items that need attention:

  • •Security or vulnerability keywords in title/labels (security, vulnerability, ssrf, cve, rce).
  • •Open bugs with no linked PR (likely unassigned or awaiting fix).
  • •Open PRs with no linked issue (ask for issue linkage or rationale).
  • •Large change labels (size:XL, size:XXL) or risky areas (e.g., web, infra).
  • •Issues labeled good first issue or status: accepting prs (good to delegate).
  • •Anything urgent, customer-facing, or cloud-related (labels like cloud).

Troubleshooting

  • •If gh fails, confirm authentication with gh auth status.
  • •If requests fail through a proxy, rerun with --no-proxy.

Manual Fallback (if script is unavailable)

Use gh directly with the same filters (repeat per repo):

bash
gh issue list -R langgenius/dify --state open --search "created:YYYY-MM-DD" --json number,title,createdAt,labels,url,closedByPullRequestsReferences

gh pr list -R langgenius/dify --state open --search "created:YYYY-MM-DD draft:false" --json number,title,createdAt,labels,url,isDraft,closingIssuesReferences

Repeat for the other repos and format the tables using the same rules above.