higress-daily-report_skill

This skill generates Higress project daily reports, tracks issue/PR activity, and records solutions to accelerate issue closure and knowledge sharing.

Go

7.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill alibaba/higress --skill higress-daily-report

README.md5.5 KB
SKILL.md6.4 KB

Overview

This skill generates daily Higress project reports to track issues and PR activity, capture resolutions, and drive community issue closure. It consolidates new items, updates follow-up status, and extracts knowledge entries to grow a searchable knowledge base. The goal is continuous tracking and closure of community-reported problems.

How this skill works

Each run fetches yesterday's issues and PRs, compares them against a persistent tracking file, and updates follow-up states based on comment activity and ownership. It classifies issues, matches them to existing knowledge entries, scores priority, and drafts recommended replies and next actions. The skill saves a markdown report, updates the issue-tracking JSON and knowledge base, and posts concise notifications to the project Discord channel.

When to use it

Generate the project daily report for team sync and community follow-up.
Identify and prioritize new issues and PRs created in the last day.
Detect stale issues over 7 days and flag for closure or revalidation.
Capture resolved issue patterns as new knowledge base entries.
Automate follow-up reminders for issues awaiting user or reviewer input.

Best practices

Run the report daily at a fixed time to maintain cadence and avoid missed items.
Keep the issue-tracking JSON authoritative: update follow_up_status after any manual intervention.
Record solution details into the knowledge base immediately after a confirmed resolution.
Use classification and priority suggestions as guidance; validate with maintainers for edge cases.
Split long Discord notifications into multiple messages under the 2000-character limit.

Example use cases

Morning digest summarizing new issues, PRs, and items needing immediate attention.
Weekly audit of stale issues to decide closure or further investigation.
Auto-suggested reply drafts for maintainers when common issues match knowledge base entries.
Post-resolution workflow: append KB entry, update tracking state, and notify contributors of closure.
Triage support: classify incoming issues by category (CORS, routing, deployment) to route to the right owner.

FAQ

Priority is suggested by impact indicators such as comment volume, labels, and matched KB severity; maintainers should confirm final priority.

What triggers marking an issue as stale?

An issue with no activity for over 7 days is flagged stale and surfaced for decision to close or re-engage.