Claude Code: Up and Running

Chapter 9. From Prompt to Pull Request

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 9th chapter of the final book. The GitHub repo is active.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

Say a friend hands you a feature idea, or you notice something in your own app that could work better. Either way, the path through Claude Code is the same: a prompt, a plan, an implementation, a stack of checks, and a pull request someone can actually review. Every feature in MockHub reached production that way, including integrations that started as casual suggestions. The distance is the lesson. In this chapter we’ll follow one feature end to end: the order-review step between cart and payment in MockHub’s checkout.

The Prompt to PR Pipeline

Feature work starts with an idea or a GitHub issue and ends with a pull request. What happens between those two points depends on scale.

At doghouse scale the trip is short enough to hold in your head. Describe the change, watch it happen, try the result, commit. If something breaks, the blast radius is one small app nobody else depends on.

At cabin scale someone is depending on the code, so the trip picks up structure. You work on a branch, you ...