Commit One Change
Make a commit called Fix typo in README that contains only the README fix, and leave scratch.txt untracked.
Short tasks, one skill each. No objectives, no hints: a scenario, a mission and a repository. GitDojo checks the end state, however you get there.
Make a commit called Fix typo in README that contains only the README fix, and leave scratch.txt untracked.
Commit theme.css as Add dark theme on a new branch called feature/dark-theme, so that main does not have it.
Mark the current commit as release v2.0 with an annotated tag, and make sure v2.0-rc no longer exists.
Bring all of feature/search into main, keeping main's footer, and end up on main.
Merge feature/retries into main so that config.js keeps both changes, a timeout of 30 and 3 retries, with the merge finished and nothing left uncommitted.
Give Add invoice export a home on a new branch called rescue, while main stays without it.
Commit the footer fix as Fix footer link on main (the link should point to /about), then be back on feature/profile with your unfinished profile.js edits in the working tree, still uncommitted, and nothing left on the shelf.
Bring your main up to date with origin's main, so it contains Add rain warnings.
Leave feature/charts with a single commit, Add charts, on top of Initial commit, with the final chart code exactly as it is now.
Make feature/export start from the latest main, in a straight line, keeping both of its commits.
Get both commits onto origin's main, with your main and origin's at the same commit, and no merge commit: history should stay a straight line.