digest-format
How to compose or revise the weekly digest email of a repository's open issues: subject line, grouping, one-line issue summaries, needs-attention and stale criteria, citation format, and the closing follow-up guidance. Load when composing this week's digest or reworking a draft of it. Not for other emails, replies, or GitHub and Linear comments.
- License 许可
- Apache-2.0
- 所属仓库
- vercel/eve
- 最近更新
- 2026-11-15
- Stars
- ★ 5.9k
- Forks
- 656
01 前言 Front Matter
- description
- How to compose or revise the weekly digest email of a repository's open issues: subject line, grouping, one-line issue summaries, needs-attention and stale criteria, citation format, and the closing follow-up guidance. Load when composing this week's digest or reworking a draft of it. Not for other emails, replies, or GitHub and Linear comments.
03 SKILL.md 正文
Digest Format
The weekly digest is one email a maintainer skims in their inbox. Everything here serves that: short, grouped, every issue cited as #N with a link, and links for follow-up in the tracker.
Before composing
- Check the user's saved preferences first. A preference like "group the digest by label" or a preferred level of detail overrides the defaults below; everything a preference doesn't cover follows this skill.
- Work only from issues fetched in this run. Never carry over counts, titles, or numbers from earlier context.
Subject line
- Name the repository and anchor the week: "Weekly issues digest: owner/repo" followed by the date, for example "Weekly issues digest: acme/widgets, June 22 2026".
- If a scheduled task dictates an exact subject format, follow the task; it wins over this default.
Structure
Open with a one-paragraph overview: total open issues, what changed since last week (new, closed, spikes), and any theme worth a sentence. Then the groups, then the follow-up guidance.
Default grouping, in this order:
- Needs attention: issues a maintainer should look at first.
- Recent activity: new this week or updated this week, ordered by most recent activity.
- Stale: open with no activity in 30 or more days. If this group is long, list the five oldest and give a count for the rest.
When the user prefers a different grouping (by label, by assignee, by milestone), use theirs and keep the needs-attention issues at the top of whatever group they land in, marked as such.
Skip any group that would be empty rather than showing an empty heading. If the repo has no open issues at all, send a short note saying so instead of the grouped digest.
What qualifies where
Needs attention, any of:
- Labeled as urgent by the repo's own convention (bug plus high-priority, regression, security, or similar).
- A question or report from a user that has sat without a maintainer response for a week or more.
- Heated or fast-moving: many new comments in the past week with no resolution.
- Blocking something the thread names: a release, another issue, a downstream user.
Stale: no comments, label changes, or other activity in 30 or more days. Staleness is about silence, not age; an old issue with fresh discussion belongs in recent activity.
An issue appears in exactly one group. Needs attention wins over the others.
Summarizing an issue in one line
Each issue gets one line: the citation, the title or a tightened version of it, then the state of play.
- The state of play is where the thread stands now, not a recap: "fix proposed, awaiting review", "reporter went quiet after repro request", "two users confirmed on 3.2".
- For a long or noisy thread, read the most recent maintainer or reporter comments and state the current position; skip the back-and-forth that led there.
- Never paste issue bodies or comment text. Numbers help ("14 comments this week") when the volume itself is the news.
Example line: #42 Crash on empty config: fix proposed, awaiting maintainer review.
Citations
- Cite every issue by number in #N form, and make the #N a link to the issue on GitHub. Readers use the number in authorized GitHub follow-ups, so it must be present and correct on every mention.
- Use only numbers and links from issues fetched this run. Never guess or reconstruct a URL.
Scannability
- The reader is triaging their inbox. Group headings, one line per issue, no walls of text.
- Keep the overview to one paragraph and each issue to one line. If an issue truly needs more, one extra clause beats a second paragraph.
- Plain text and simple lists render everywhere; skip tables and heavy formatting.
Closing
End every digest with links for follow-up in the tracker. Maintainers with write, maintain, or admin permission on the configured repository can also @Kody there to request action. State that email replies are not processed. Never invite the reader to reply by email.
04 同仓库更多 Skills
writing-quality
The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.
writing-quality
Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.
seo-aeo-best-practices
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity/functions, @sanity/blueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.
portable-text-serialization
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.
portable-text-conversion
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext/markdown (markdownToPortableText), @portabletext/block-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.