Corey for Engineering teams

Triage, draft, ship. The repo housekeeping, handled.

Corey runs the issue triage, first-pass replies and routine changes that pull engineers out of flow - and tees the results up for review. Nothing merges without a human.

Hire Corey for 28 days at no cost → How it works

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 pain

Sound familiar?

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

Run the housekeeping around your codebase.

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.”

A day with Corey

09:00

Corey has triaged the overnight issues - labelled, deduped, six replies drafted for the FAQs. An engineer approves the batch.

11:30

You ask it to handle the queued dependency bumps. It opens PRs, runs the checks and tags reviewers. Nothing merges on its own.

14:00

A gnarly bug comes in. Corey reproduces it, writes clean steps and points at the likely commit, saving an hour of digging.

17:00

It drafts the release notes from today’s merged PRs. You read, trim and ship.

Questions

Common questions.

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.

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.

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.