List open pull requests in this repository that have waited more than 24 hours for a first review or more than 48 hours since the last update. Group by author, show requested reviewers, and suggest who could review based on recent changes to the same files.
Outcome: A daily list of stuck PRs with suggested reviewers.
Connectors: Connectors may not be on for your account yet. If they are not in the Customize view, add the service as an MCP server where your admin allows it, or attach an export.
Connect the chat and error-tracking sources the automation needs, such as Slack or a Sentry MCP server.
Create a daily automation with the prompt and the smallest tool set that works.
Read the first week of reports yourself before you trust it to open PRs unattended.
Collect feedback from <Teams or Slack channel> and errors from <error tracker> for the last 24 hours. Group them into distinct problems, match each to an existing issue or open a new one, and investigate the top three. For any with a clear fix, open a pull request with a test and confirm CI passes. Report what you did and what needs a human.
Outcome: A daily loop from user signal to reviewed fix PRs, with a report of what still needs people.
Read the design doc below and the code it affects. Propose a breakdown into issues of one to three days each, with acceptance criteria, dependencies and a suggested order. Show me the list before creating anything.
<paste design doc>
Outcome: A reviewed issue breakdown created from your repository templates.
Look at issues and pull requests from the last 60 days and find recurring manual chores, such as dependency bumps, flaky test reruns or release checklists. Rank them by how often they happen and propose an automation prompt for the top one.
Outcome: A ranked chore list and a ready-to-save automation.
Write an onboarding guide for a new engineer joining this repository. Cover the architecture, how to build and test, the five most important directories, common pitfalls from recent bug fixes and three good first issues that are open now.
Outcome: A current onboarding guide based on the code as it is today.
Draft my weekly team update. Include work shipped, work in review, anything blocked, risks to the current milestone and one highlight per person based on their merged pull requests. Keep it under 300 words.
Outcome: A grounded status draft you edit and send.
