For creatorsMake videos about AI coding? Earn 50% for life.Earn 50% for life.Become a Morphy creatorJoin →
morphy
Download

Flow template · Development

Small change

A builder in its own copy opens a pull request; a reviewer reads it on GitHub until it’s ready for you to merge.

2 chats1 noteWorks on a repositoryAny AI Morphy connects

Download dev-small.flow.jsonUse it in Morphy

Shared by MrApers · 25 October 2026

Small change: the flow's shapeStart hands what you type to Builder. Builder hands its answer to Reviewer. Builder's answer is added to Ready to merge, a note. Reviewer hands its answer back to Builder: a loop that goes round until the work is done.StartBuilderown copyReady to mergenoteReviewerthe repository
Left to right, as Morphy lays it out on your canvas: the Start, then each step.

What it does

For a fix or a small feature. The builder works in its own copy of your repository (a git worktree on its own branch), runs the tests and opens a pull request. The reviewer reads it with GitHub’s command line and leaves its review there; the builder fixes what it asks for on the same branch, until the reviewer approves. Then the run ends, and the pull request waits for you to merge. Needs git and GitHub CLI (gh), signed in.

Its brief, which every chat in it works to: Changes go through a branch and a pull request, and the user merges. Never push to the main branch, force-push or delete branches.

Each step

  1. Builderin its own copy of the repository: You work in your own copy of the repository, on your own branch. Make the change you are asked for, run the tests, commit, `git push -u origin HEAD`, then `gh pr create --fill`. Answer with the pull request’s link and a short summary. When the reviewer asks for changes, fix them on the same branch, push, and answer with the same link. When its answer starts with APPROVED, answer with the link and “Ready for you to merge.”
  2. Ready to merge: A note: every answer that reaches it is added at the end, under who sent it and when.
  3. Reviewerin the repository: You get a pull request’s link. Read it with `gh pr view <link>` and `gh pr diff <link>`: does it do what was asked, and does nothing break? Leave your review on GitHub (`gh pr review <link> --comment -b "…"`, or `--request-changes`). Answer `APPROVED <link>` when it is ready to merge, else the changes to make, as a short list.

How the work moves

  • Start hands what you type to Builder.
  • Builder hands its answer to Reviewer.
  • Builder's answer is added to Ready to merge, a note.
  • Reviewer hands its answer back to Builder: a loop that goes round until the work is done.

What you need

  • A git repository on your computer, with at least one commit
  • Git, and GitHub’s command line (gh), signed in with gh auth login
  • Any AI Morphy connects: Claude Code, Codex and the rest

Every change goes through a branch and a pull request, and you merge. Morphy gives each chat that changes code its own copy of your repository, next to it (a git worktree on a branch of its own).

Use it

  1. In Morphy: Settings → Community → Playground → Flow templates, pick Small change and click Use this flow. Morphy asks which repository it works on, then builds it.
  2. Or from the file: download dev-small.flow.json and, on the same page, click Import a file…. It's yours to change, too.
  3. Start it: click Start on the flow and say what it should do.

More development templates

Every flow template
Download MorphyShare a flow of your own