# Corey for Engineering teams

Corey for engineering teams runs the repo housekeeping that pulls developers out of flow - issue triage, first-pass replies, routine PRs, bug repros and release notes - and tees the results up for review. Nothing merges without a human.

## The problem
- Issue triage is constant, context-heavy and nobody’s job.
- The same questions get answered in issues again and again.
- Small, routine changes pile up behind the work that needs real thought.
- Release notes and changelogs get written from memory, late.

## What Corey does
- Issue triage: “Triage today’s issues, label them, group duplicates and draft replies for the questions.”
- First-pass PRs: “Open a PR for that dependency bump and run the checks, for me to review.”
- Repro and reports: “Reproduce this bug, write up the steps and link the likely cause.”
- Release notes: “Draft the changelog for this release from the merged PRs.”
- Stale cleanup: “Find issues with no activity in 60 days and propose closing or pinging.”
- Scheduled jobs: “Every night, run the backup, check the build and post the result.”

## FAQ
Q: Does Corey write code that gets merged automatically?
A: No. It opens first-pass PRs, runs the checks and tags reviewers, but nothing merges without a human. It handles the routine changes so engineers review instead of building boilerplate.

Q: What repo work can it handle?
A: Issue triage and labelling, drafting replies to common questions, dependency bumps, bug repros with steps, stale-issue cleanup and drafting release notes from merged PRs.

Q: How does it connect to our codebase?
A: Over MCP, from inside Claude Code. You grant the repos and tools it can touch; it works in those and reports back. No code or data leaves for another platform.

Pricing: 28 days on us, no card. GBP 49/month or GBP 490/year after that, cancel any time. Start with Corey: https://getcorey.ai/get-started