Ten fixes, ten commits
Use with: ship-on-github. Resume line when done: Comfortable improving existing codebases — see {project_name} commit history
Brief
Clone a small template project and make ten distinct improvements to it, one commit each, using at least one branch and one merge. The skill on display is surgical change: each commit does one thing, says what it did, and leaves the project working.
Personalize
- The base project. A small open template you can actually run: a starter site, a tiny game, a CLI example. Your agent can suggest three; you pick the one you understand least, on purpose.
- The ten improvements. List them in the README before starting: fix a bug, improve wording, add a small feature, tighten styling. Real improvements you can defend, not ten typo fixes.
Milestones
- Base project cloned into your repo, running locally, README lists the planned ten improvements.
- Improvements 1–3 committed, one commit each, project still runs after every commit.
- Improvements 4–7, at least one done on a branch and merged.
- Improvements 8–10; update the README list to what actually happened and why any plan changed.
Done means
- Repo on your GitHub account, project runs
- Ten improvement commits, each one change, each message specific
- At least one merged branch
- README maps the plan to the final history in your words
- At least 10 commits across at least 5 distinct days, authored by you
- SESSIONS.md has an entry per session, written by you