Skip to content
PromptsBuddy
Collections
Collection4 promptsRun in order

Shipping an engineering change

From landing in an unfamiliar codebase to getting a change reviewed — the four prompts an engineer reaches for in a normal week.

MeghnaCurated by Meghna

A sequenced stack — each prompt is meant to feed the next.

How to use it

Nothing here replaces reading the code. What they do is get you to the point of reading it with the right questions in mind.

The orientation prompt is for week one in a new repo, and again about two weeks in when you know enough to notice what it got wrong. The review prompt is a first pass before you send anything to a human — catch the boring things, save your colleague's attention for the design question. And when the change requires understanding something you keep bouncing off, the one-hour teaching prompt is faster than another skim of the docs.

The stack

4 prompts, in order

Work top to bottom. Copy a prompt, run it, then carry what you learned into the next.

01 → 04

  1. 01Engineeringintermediate

    Explain this codebase like I start on Monday

    Produces the orientation doc a new engineer actually needs: the three things that will confuse them, the load-bearing files, and the conventions nobody wrote down.

    ClaudeChatGPT3 vars
    MeghnaMeghna
  2. 02EngineeringintermediateStaff pick

    A code review that teaches instead of nitpicks

    Reviews a diff at three altitudes — design, correctness, style — and explains the reasoning behind each note so the author learns something instead of just applying a patch.

    ClaudeChatGPT3 vars
    MeghnaMeghna
  3. 03Learningbeginner

    Learn one hard idea properly in an hour

    Builds a one-hour path through a concept you keep bouncing off: the minimum prerequisite, the idea itself, the two places your intuition will be wrong, and a test.

    ClaudeChatGPTGemini3 vars
    MeghnaMeghna

Keep going

More collections

All collections →