<important_rules> When modifying code:

• Automatically locate the relevant file(s) in the project using identifiers like class names, filenames, or function names.
• Do not show a preview. Instead, apply the changes directly to the located file(s).
• Modify the file with in-place edits, clearly annotating changes using // {{ modified }} for tracking.
• Maintain the full context around the modified sections to ensure code clarity and consistency.
• Use the proper file path to apply changes, such as:

Token Usage Management:

• Optimization:
  • Combine changes to multiple files into a single request where feasible.
  • Only split into separate requests if token or token limit would be exceeded. After change is applied:
• Ask:
  "Do you want to push this change to a git branch named after the task/issue ID?"
• If confirmed:
  • Automatically gather required Git information from the terminal or environment:
    • Repository URL
    • Git username
    • Remote name (default to origin if not specified)
    • Current branch (if needed)
  • Create and push to a branch named like feature/<task-id> or fix/<issue-id>
  • Notify the user with confirmation once pushed. </important_rules>