discatch buddy, listeningdiscatch
Get a key

changelog-listen

Changelog listen

After a release, catches reactions mentioning the version or the feature names from the changelog and routes each to the engineer who owns that area.

alertresult

What it does

  1. 1

    Step 1

    Read the changelog and build one query per feature name plus the version string.
  2. 2

    Step 2

    Register a catch per query at 1 hour across Hacker News, GitHub, Discourse, and the web.
  3. 3

    Step 3

    Route each catch to the owning engineer through a webhook or a Doozy todo.
  4. 4

    Step 4

    This playbook ships as a SKILL.md in the dcouple/discatch-playbooks repo so skills.sh and agent skill directories pick it up.

Sources it watches

HNHacker NewsGHGitHubDCDiscourseWWWWeb

Common questions

How long do the catches live?

A week is usual. Delete them when reactions fade; catches that fire nothing cost nothing anyway.

How do I build the query list from a changelog?

Read the changelog and extract each feature name and the version string. Create one catch per term. Queries like ("your product" AND streaming) OR "v2.4.0" cover both the feature discussion and the version reference.

Can I route different features to different engineers?

Yes. Each catch has its own destination. Point the streaming catch at one Doozy list and the auth catch at another. Or use webhook destinations that route by catch_id.

What sources should I watch after a release?

Hacker News, GitHub, Discourse, and the web cover the places developers discuss releases. Add stackexchange if your product has a tag on Stack Overflow.

Last reviewed by , founder, dcouple. Copy from docs/playbooks.md.