Skip to content
agentusehub
Sign in+ Submit
Software & DevOpsAny

Set up weekly changelogs and fix docs from GitHub issues

Neon's docs team has Devin create the weekly changelog from a playbook and open or revise doc PRs from GitHub issues, for repetitive work only.

Read the experience
Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

Neon's docs team has Devin create the weekly changelog from a playbook and open or revise doc PRs from GitHub issues, for repetitive work only.

Read the original report ↗

Reported experience

  1. What they did

    Neon's docs team standardized the weekly changelog setup as a Devin Playbook, so they only tell Devin to set up the changelog for this Friday. For GitHub issues, they point Devin at an issue, and it reviews the code, finds the docs that need updating, and creates or revises a PR.

  2. How it went

    This helped them work through a backlog of older docs issues without auditing each one by hand. Devin struggled with open-ended tasks, and a bulk term rename needed 20+ manual cleanup commits.

  3. Worth knowing

    Keep tasks clearly scoped. Devin failed silently on vague jobs, with no clarifying questions or error signals, so check in on its progress yourself.

Example prompts

Try with Devin
In my docs repo at [path to repo], read the open GitHub issues labeled [label] and make the doc changes each one asks for, one branch per issue. Also draft this week's changelog from [source, e.g. merged PRs since last Friday] following the format in [example changelog file]. Pause and show me each diff before opening any PRs.

Related use cases

Software & DevOps

Port a Chrome extension to Safari

The author had ChatGPT take the Session Buddy extension source from Chrome, port it to Safari and install it, taking about 20 minutes.

ChatGPT