Integrations
Project update · GitHub + Slack
See what changed.And what needs you.
Write a project update from GitHub and Slack in one request. Through CoreSpeed, your agent lists the recent pull requests and reads the team's Slack discussion, then drafts one update that keeps merged work, open reviews and undecided questions apart. It uses your own accounts, drafts in your agent, and merges or posts nothing.
Give this to your agent
set up https://corespeed.io/SKILL.mdConnect GitHub and Slack after setup. Each account needs its own authorization.
The work and its context,in one update.
Requests you can make once GitHub and Slack are connected. The data is fictional.
- GitHubacme/app · pull requests
- #42New first-run checklistMerged
- #44Updated setup copyReview
Repository activity
Illustrative source · Fictional data
- Slack#product
- MMira10:20Let’s review the customer feedback before we scope the next release.
- RReid10:24The next release scope is still open.
Team context
Illustrative source · Fictional data
- CodexAnswer
Project update
The week, in perspective.
- The first-run checklist was merged.
- Review the setup copy.
One result to review
Nothing sent or changed
A clear status.A useful follow-up.
Put repository activity beside the project context. Completed work, current discussion, and open decisions stay apart.
Reads fromGitHubSlack
GitHub on its own →Review recent GitHub pull requests and the Slack project discussion. Draft an update with what merged, what the team is discussing, and what needs a follow-up. Do not post it.
github__list_pull_requestsok
1 merged, 1 waiting for review
Keep your agent.Bring the context.
One CoreSpeed account, across compatible agents.
- 1
Set up CoreSpeed
Give your agent the setup line. It adds CoreSpeed and signs you in.
- 2
Connect GitHub and Slack
Authorize each account and the content this task needs.
- 3
Ask for a project update
Name the project or conversation, then review the result.
Setup guidesClaude CodeCodexCursor