dotcom-release-crew

Identifies critical contributors in the production...main commit range and posts release mentions to Discord.

50.1k|3.5k|Updated May 9, 2021
One-click install
npx skills add https://github.com/tldraw/tldraw --skill dotcom-release-crew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotcom-release-crew
Source: https://github.com/tldraw/tldraw/tree/main/skills/dotcom-release-crew
Command: npx skills add https://github.com/tldraw/tldraw --skill dotcom-release-crew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly tldraw.com releases require knowing which engineers own critical fixes or significant features so they can be on hand during the release. Manually reviewing the production...main commit range and pinging the right people in Discord is repetitive and error-prone.

Core Features & Use Cases

  • Commit Range Analysis: Fetches every commit on main not yet on production via the GitHub API, with author and subject line for each squash-merged PR.
  • Critical Contributor Selection: Filters out docs, chores, tests, and trivial fixes, then ranks authors by release risk to produce a tight list of 2-3 people.
  • Discord Notification: Posts a formatted summary to the #development channel via webhook, using Discord user ID mentions so the right people get pinged.
  • Use Case: During the weekly dotcom release, run this Skill to automatically determine that a sync fix and an editor feature are shipping, then ping their two authors in Discord with a link to the diff.

Quick Start

Ask the assistant to identify who should be involved in this week's dotcom release and post the release crew to Discord.

Frequently Asked Questions about dotcom-release-crew

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find who contributed critical changes to a release?

Fetch the commit range with the GitHub API comparing production...main, filter out docs, chores, and trivial fixes, then group remaining commits by author. Rank authors by release risk and keep the top 2-3 contributors.

How do I post a message to a Discord channel using a webhook?

Send a POST request to the webhook URL with a JSON body containing a content field. Build the JSON with jq to escape newlines and quotes safely, and set allowed_mentions to control which pings actually fire.

How do I mention a specific user in a Discord webhook message?

Use the format <@USER_ID> with the user's numeric Discord ID in the message content, and include allowed_mentions with parse set to ["users"]. This pings only those users while preventing @everyone or role mentions from firing.

What environment variables does this release workflow need?

It requires DISCORD_RELEASE_WEBHOOK_URL for posting to the #development channel and GH_TOKEN for the gh CLI to query the GitHub compare API. If the webhook variable is unset, the workflow stops and asks you to set it.

What are the limitations of comparing production...main for releases?

During SDK freeze weeks, production may ship cherry-picked hotfixes while main keeps moving, so the range can miss production-only hotfix authors and include unreleased main work. The comparison is most accurate during the normal weekly main-to-production promotion.