Grooming for agent-written repos

Agents write
the code.
Nobody cleans
it up.

Copilot and Cursor solved the writing. Nothing watches what gets left behind. CodePanzee reads every agent pull request and finds the duplicate helper, the assertion that got loosened, the file nothing imports, the doc that stopped being true. Then it opens the pull request that deletes them.

GitHub and GitLab at launch. One email when it opens.

✓ On the list. We will mail you first.

What it catches

Per pull request

Duplicate logic

The agent wrote a fresh slugify. You already had two, in two different folders, with two different edge cases.

Softened tests

Assertions widened, cases skipped, mocks that pass whatever you feed them. The suite still goes green and covers less.

Orphaned files

Modules nothing imports, kept alive only by the test that was written alongside them and never read again.

Docs that drifted

The README describes a function that was renamed four merges ago. Your next agent reads it as ground truth.

Most of our pull requests are subtraction.

CodePanzee does not suggest more code. It ships a reviewable diff that takes code out, with the reason attached to every line, and it will not touch anything still reachable from a real call path.

codepanzee/groom-482 · src/utils
export function slugify(str) { ... } dup of lib/text.ts:14
export const toKebab = (s) => ... dup of lib/text.ts:14
import legacyFormat from './legacy' no reachable caller
test.skip('handles unicode slugs') skipped 61 days
re-point 7 imports to lib/text.ts
restore unicode case against lib/text.ts
4 files removed · 1,240 lines deleted · coverage +2.1%

Coming soon

A product of INVENDAR LABS↗

Invendar Labs builds original products. Studio and Systems build for clients.