Agree on PR rules before a teammate sends a 5,000-line vibe-coded PR

A developer wrote about his business partner sending a 5,000-line vibe-coded PR he had not tested.

Difficulty
BeginnerOur rating
Time to build
n/aOur estimate
Monthly cost
Not reported
Revenue
Not reportedWe only show revenue the source states
Engagement
No public countThe source shows no number

What they did

yhcj describes receiving an untested 5K-line AI-generated PR from his business partner.

How it went

The post sparked an HN discussion about review norms.

Worth knowing

Agree on PR size limits and testing before everyone uses agents.

Builder recipe

Our own starting point, written from the source. Adapt it to your setup.

Stack

  • PR template
  • CI tests

Steps

  1. Set a maximum PR size.
  2. Require tests and a self-review note.
  3. Have the agent split big changes.

Starter prompt

Split this change into PRs under 400 lines, each with tests and a note on how I verified it.

Tags

Tool GitHub
Industry Software

Read the original

Related use cases

The Daily 5.

Five real AI agent use cases each morning, each with a recipe and a source. Plus a Sunday roundup. Free.