alphakek-ai/Dev Updates

AI-powered dev update notifications with privacy modes and multi-channel dispatch

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Jun 6, 2026
License: Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned

uses: alphakek-ai/dev-updates-action@1d840cf6378c76392f130f3eff6c45c119be1b6e # v1

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
channels	YAML list of channel configurations	yes	—
cooldown	Minimum time between notifications (e.g., 6h, 1d, 30m). Empty = post on every push.	no	""
community_rules	Instructions for community-facing summaries (user value, no internal details)	no	Audience: end users who do not know the codebase. Each bullet must answer "what can I now do, or what got better for me?" — lead with the user benefit, in plain language. Translate every change into user value. ("Upgraded to model X with speculative decoding" -> "AI responses are noticeably faster, especially on long answers.") If a change has no observable user impact, omit it or fold it into a single generic "behind-the-scenes improvements" bullet — do not pad the list with internal work. Do NOT name files, functions, libraries, model names, databases, or infrastructure. No version numbers, no product/tech brand names. If you catch yourself naming a technology, restate it as the benefit it delivers.
dev_rules	Instructions for developer summaries (architecture & business logic)	no	Audience: the dev team. Explain HOW the system changed — the business logic, architecture, and data flow — not a file-by-file inventory. For each bullet, lead with the behavioral/structural change ("X now does Y instead of Z", "responsibility for X moved from A to B"), then cite the file/function/symbol as supporting evidence in parentheses or a trailing clause. Never make a filename or variable name the subject of a bullet. Group related file changes into one conceptual change. If five files moved because one component was replaced, that is ONE bullet about the component, not five about the files. Call out anything that changes contracts: breaking changes, migrations, new/removed env vars, API shape changes.
title_style	Style for the update title	no	catchy, under 40 chars
max_bullets	Maximum number of bullet points per summary	no	5

Outputs

no outputs