Let's begin by reviewing our objective.

Objective: Stage and commit the code changes for the new score limit feature to the 'feature/add-score-limit' branch. Use a clear and descriptive commit message (e.g., 'feat: Add score limit to end game').

Next, we'll perform initial verification steps to understand the current state.

Your specification is to save the code changes you made in the previous step using Git.

Use git status to see the current state of your working directory and staging area. You should see the main.py file listed as modified.

Now, let's build the solution by following the instructions to stage and commit your changes.

Step by step checklist:

1. Stage the modified main.py file to prepare it for committing.
2. Commit the staged changes with a descriptive message indicating the addition of the score limit feature.

The following documentation sections are going to be helpful:

• Saving Your Work (Committing to a Feature Branch)
• Stage changes
• Commit changes

With the changes in place, let's re-verify our work to ensure it meets the specification.

Use git status again to confirm that there are no uncommitted changes in your working directory.

Use git log --oneline to view the commit history and confirm that your new commit is at the top of the history for the current branch (feature/add-score-limit).

Verification Results:

• ✅ git status shows no uncommitted changes.
• ✅ git log --oneline shows a new commit with a descriptive message on the current branch. All verification steps passed!