Map an unfamiliar codebase and plan a first contribution

Laura Salinas pointed a Kiro Crew bot at a fresh clone of HeyGen's HyperFrames repo and got an architecture report and a first-contribution plan in about 10 minutes.

Done withKiro· Nov 18, 2026

What they did

Laura Salinas cloned HyperFrames, HeyGen's open source project for rendering HTML and CSS animations into MP4 files, and wanted to get oriented in it without reading folders by hand. In the Kiro Crew desktop client she created a bot, named it, pointed its workspace at the local clone and gave it a single sentence: help her understand the code well enough to make a first contribution. The bot split that goal into tracked items, each with its own acceptance condition, and sent parallel worker sessions to read different parts of the repo. It kept a dashboard of milestones and a memory of the repo that carried over to the next day.

How it went

About three minutes after it started working, the bot returned a report on the repo's structure and a plan for a first contribution. She puts the whole run, from clone to map, at roughly 10 minutes against what would usually take her most of an afternoon. The next day she resumed the same chat and the bot answered follow-ups from memory without rescanning. One snag: after she approved the goal and the suggested milestones, the bot sat idle until she told it to start.

Worth knowing

The author writes for the AWS organisation on dev.to, so this is a vendor employee trying the vendor's product. Expect to nudge the bot after approving milestones, and keep the goal to one narrow sentence; she found a broad goal gives it no clear finish line.

Try it

With Kiro· 3 parts to fill in

You are working in a local clone of [repo name] at [path to clone]. My goal: understand this codebase well enough to make my first contribution. Break that into a few tracked items, each with a clear acceptance condition, and read the relevant parts of the code for each one. Produce a short architecture map: where execution starts, the main modules and how they connect, how to build and run the tests. Then list [number] good first issues or small changes I could make, with the files each one touches. Do not edit any files. Stop and show me the report when every item meets its acceptance condition.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related