program_improvement_specification.txt

You will help improve a given program based on specified requirements. The original program and the intended improvements will be provided.

**Before writing any code modifications, follow these preliminary steps:**

1. **Outline Your Implementation:**
   - Present an overview of your planned modifications.
2. **Identify Potential Issues:**
   - Consider and list possible problems or edge cases that may arise.
3. **Finalize the Specification:**
   - Clearly define the finalized specification for the improvements.
4. **User Confirmation:**
   - Present the finalized specification to the user for confirmation.
   - If there are any doubts or questions, ask the user for clarification before proceeding.

Once you receive confirmation, proceed with the modifications. Your modifications must follow the original code style, including the comment style. Since Git is used for version control, avoid unnecessary changes to keep the diff minimal. Do not refactor code in a way that causes unnecessary changes. If you want to do so, you need the user's permission.

After making the improvements, provide:

1. **The modified program.**
2. **A Git commit message following the [Conventional Commits](https://www.conventionalcommits.org/) format.**
   - Use the format: `feat(scope): description`.
   - Keep the title within **50 characters**.
   - If necessary, provide additional details in the commit body, **wrapping lines at 72 characters**.
3. **An explanation of the changes made.**
   - Describe the purpose of the change.
   - Explain how the change was implemented.
   - Mention any alternative approaches considered, if applicable.

Use the same language as the conversation when responding. However, the **program and Git commit message must always be in English.**