prod-commits

Generate a Slack promotion message listing commits for an AirSync service.

Updated Jun 7, 2025
One-click install
npx skills add https://github.com/erazemk/dotfiles --skill prod-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prod-commits
Source: https://github.com/erazemk/dotfiles/tree/main/agents/skills/prod-commits
Command: npx skills add https://github.com/erazemk/dotfiles --skill prod-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly craft a Slack promotion message that clearly communicates which commits will be promoted to production for a given AirSync lambda service, reducing manual drafting time and minimizing miscommunication.

Core Features & Use Cases

  • Automated promotion briefing: Generate a concise Slack-ready list of commits that will be included in production deployment.
  • Contextual service detection: Infers the target service from the current repository or directory context.
  • CC and ownership handling: Identifies relevant codeowners and formats CC list for Slack.
  • Use Case: When preparing a prod deployment announcement, generate a ready-to-send message for the engineering channel.

Quick Start

Provide a ready-to-send Slack promotion message for the current service context.

Frequently Asked Questions about prod-commits

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

FAQPage Schema
How do I automate Slack deployment announcements for production commits?

Automating Slack deployment announcements involves generating a formatted list of production commits, including short hashes, dates, subjects, and authors. This Skill extracts the service name from the repository, identifies the production baseline, and formats new commits from origin/main into a ready-to-send message.

How do I format a Slack message for a production deployment promotion?

Formatting a Slack promotion message requires listing commits to promote to production with linked short-hashes, dates, subjects, and authors. The Skill automatically structures these details and CCs non-poster codeowners using their Slack IDs for clear ownership tracking.

Can I automatically CC codeowners in Slack deployment notifications?

Yes, you can automatically CC codeowners in Slack deployment notifications. The Skill identifies non-poster codeowners from the repository context and formats their Slack IDs into a CC list within the generated promotion message.

What is the best way to list commits for a production promotion announcement?

The best way to list commits for a production promotion announcement is to identify the production baseline commit and gather new commits on origin/main. This Skill automates that process, formatting each line with a linked short-hash, date, subject, and author for engineering channels.

Does this deployment promotion tool work without specific external dependencies?

Yes, the deployment promotion tool works without external dependencies. It operates autonomously to derive the service name from the current repository, identify the production baseline, and gather new commits on origin/main to draft the promotion message.

Why should I use an automated tool for production deployment promotion messages?

Using an automated tool for production deployment promotion messages reduces manual drafting time and minimizes miscommunication. It ensures consistent formatting of commit details and accurate codeowner CC lists, streamlining the announcement process in engineering channels.