Describe what you want, and ProPR turns it into a short list of small tasks, builds them, and hands you each result as a change you can read and try before it goes in. Six worked examples show the path for a brand-new project and for code you already have.
Software grows well when its changes are small enough to look at, which is what GitHub was built for. ProPR puts you on that path from the first minute, with no commands to learn.
When something goes wrong, you can see which step did it and revert that pull request from GitHub while the rest of the project stays as it was. The glossary defines these words and a dozen more.
The walkthroughs follow the same five steps, and once learned they carry you through any project.
A repository is the folder on GitHub that holds your project and its history. Create one on GitHub, tick Add README, and add it in ProPR from the Repositories page. For an existing project, add the repository you already have.
Write a few plain sentences about the finished thing: who it is for, what it must do, what it should look like. The planner comes back with a plan: three to eight small tasks, each with a title and a checklist of what done means. Change anything you like in the plan chat, then approve it. ProPR files each task as a GitHub issue.
Each issue runs in its own clean workspace, on its own branch. When the agent finishes, ProPR opens a pull request with a summary of what it did, the tests it ran, and, for anything with a screen, a picture of the result.
Read the summary, look at the picture, open the preview. If you want it different, write a comment in your own words and a new commit arrives on the same pull request. Ask a second model to review it when you want another opinion, and press merge when you are happy, which is the moment the change becomes part of your project.
The next feature is the next plan. Hand a bigger outcome to a goal and check in on its progress, or put the routine work on a schedule with an automation. The project stays easy to steer because the work still arrives as pull requests.
Four project types, each with a recommended stack, the first prompt, the plan it becomes, and the pull requests that follow. The projects are examples written to show the steps.
A landing page on Astro and Cloudflare, built one reviewed pull request at a time.
An internal tool on Next.js and Supabase: sign-in, data, charts, one pull request per piece.
A 2D game on Phaser, each level, menu and sound landing as its own reviewed change.
An Expo app you test on your own phone, built screen by screen in reviewed pull requests.
ProPR joins a project at any age. Start with one small issue and build trust one pull request at a time.
From one small issue to a planned feature in a week, without changing how the code ships.
Pin the behaviour with tests, refactor in small reviewed steps, then add the features that waited.
Everything in these walkthroughs happens in a browser. ProPR Hosted gives you your own instance, run by the ProPR team, with your AI subscription or API key plugged in. The live demo lets you click through plans and pull requests before you commit to anything.
On your own server, self-host ProPR, free and open source.
All guides