Weekly issue digest
By Toolspoke
Reads GitHub each Monday and posts a digest of the week's new issues to Slack.
Needs a Toolspoke account. You choose which project it installs into.
GitHub
Slack
Its last step
Count what closed in the same week
- GitHub + Slack
- Required integrations
- Runs on a schedule
- Mondays at 9am by default
- Count what closed in the same week
- What its last step does
- Nothing destructive
- 0 of 37 actions in its tools
On this page
The short version
- What it is
- Reads GitHub each Monday and posts a digest of the week's new issues to Slack.
- Works with
- GitHub, Slack
- How often
- Mondays at 9am, once you switch it on.
- What it never does
- Comment on, label, assign, close or reopen an issue.
- What you need
- A Toolspoke account, with GitHub and Slack connected.
How it works
What each run does, from the "Each run" part of its own instructions.
- Step 1:
Fix the window from the same hour last Monday to now. Use the issue's created date, not its updated date, or old issues with a new comment will look new.
- Step 2:
List the issues in each repository with list_issues, open and closed, created in the window. Leave out pull requests; GitHub returns them from the same call.
- Step 3:
Group them by label
Issues with no label go in their own group, and that group goes first, because an unlabelled issue is one nobody has looked at yet.
- Step 4:
Mark the ones that need attention anything labelled as a bug or with a severity label, anything opened by someone outside the organisation, and anything with more than five comments already. Say why each one is marked.
- Step 5:
Count what closed in the same week and say it in one line, so the reader can see whether the backlog grew.
What you get
How the agent's own instructions describe what it hands back. Install it to see a real result.
Count what closed in the same week and say it in one line, so the reader can see whether the backlog grew.
Integrations & requirements
Weekly issue digest needs GitHub and Slack to work. You sign in to each one yourself.
GitHub
RequiredManage repositories, issues, pull requests, and Actions.
Authentication: Personal access token
Slack
RequiredSearch conversations and send messages to your workspace.
Authentication: Bot token
Skills it follows
| Tool | Actions it offers |
|---|---|
| GitHub | 26 in all: 16 read, 10 write, 0 destructive. Nothing that deletes or permanently changes anything. |
| Slack | 11 in all: 7 read, 4 write, 0 destructive. Nothing that deletes or permanently changes anything. |
A project can switch any action off, and every call is logged. The counts are what each tool offers; which of them the agent uses is up to its instructions.
What it will never do
- Comment on, label, assign, close or reopen an issue.
- Include issues from a private repository in a channel that people outside the team can read.
If something goes wrong
If a repository cannot be read, name it in the post and carry on with the others. A digest with one gap is still useful; no digest is not.
These are written into Weekly issue digest's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.
When it runs
Weekly issue digest runs mondays at 9am by default. Its routine arrives switched off. Turn it on when you are ready: every run costs your workspace money.
Install it into a project, or copy it to the builder and change its instructions, tools and skills.
Use Weekly issue digest
Pick a project and connect the tools it needs.