# See what changed. And what needs you.

Source: https://corespeed.io/integrations/github-slack

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.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect GitHub and Slack after setup. Each account needs its own authorization. Create an account: https://app.corespeed.io/sign-up

## A clear status. A useful follow-up

Put repository activity beside the project context. Completed work, current discussion, and open decisions stay apart.

You ask your agent: "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."

It calls CoreSpeed:

- `github__list_pull_requests`: ok, 604 ms
- `slack__conversations_history`: ok, 447 ms

It reads from: GitHub, Slack.

### Project update: The week, in perspective.

The new onboarding checklist is merged. The setup copy is awaiting review, and the team has not agreed on the next release scope.

**Completed**

- The first-run checklist was merged.

**Follow up**

- Review the setup copy.
- Use the customer feedback discussion to agree on the next release scope.

_Illustrative result from fictional sources · Nothing sent or changed_

GitHub on its own: https://corespeed.io/integrations/github

## The work and its context, in one update

Requests you can make once GitHub and Slack are connected. The data is fictional.

### Repository activity

GitHub · onboarding work · GitHub

- Merged: New first-run checklist
- Open review: Updated setup copy
- Illustrative source · Fictional data

### Team context

Slack · product discussion · Slack

- Discussion: Review customer feedback
- Not decided: Scope of the next release
- Illustrative source · Fictional data

### One result to review

Project update · Draft in your agent

- Completed: The first-run checklist was merged.
- Follow up: Review the setup copy.
- Nothing sent or changed

## 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 guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Does this merge code or publish the update?

No. This example reads project context and drafts an update in your agent. It merges nothing, changes no issue, and posts no message.

### Do I need both connections?

Yes. This example combines GitHub and Slack. Connect both, or start from one app: an agent cannot use data it cannot access.

### Does this send or change anything on its own?

No. These examples read context and draft a result. Sending or changing a record is a separate tool call, which approvals can hold for a person. How approvals work: https://corespeed.io/docs/approvals

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

Every tool and price: https://corespeed.io/catalog/github

Every tool and price: https://corespeed.io/catalog/slack

## Related pages

- [Project update with GitHub and Linear](https://corespeed.io/integrations/github-linear): Bring GitHub changes and Linear project work into one update, with completed code and remaining work kept apart.
- [GitHub for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/github): Turn GitHub issues and pull requests into a clear project update inside your agent, without the tab tour.
- [Slack for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/slack): Bring the Slack conversation into your agent. Find the decisions, the open questions, and what happens next.

## Sources

- Connectors: https://corespeed.io/docs/connectors

Reviewed 2026-11-07.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)