sidekick.nvim

Here’s how sidekick.nvim would assist with your request to refactor the Python class in `src/utils.py`:

1. **Next Edit Suggestions**: Sidekick.nvim detects the Python file and suggests a refactor to align with PEP 8. The AI assistant highlights the class `DataProcessor` and proposes:
   ```python
   class DataProcessor:
       def __init__(self, input_data):
           self.input_data = input_data
           
       def process(self):
           # Logic here
           pass
   ```
   becomes:
   ```python
   class DataProcessor:
       def __init__(self, input_data):
           self.input_data = input_data

       def process(self):
           # Logic here
           pass
   ```

2. **Review Diffs**: The diff view in Neovim shows the changes side-by-side. You can navigate between hunks using `]c` and `[c` (standard Neovim motions). Sidekick.nvim also provides a summary of the changes:
   - Added blank line after `__init__` method (PEP 8 compliance).
   - No functional changes; purely stylistic.

3. **Apply Changes**: Press `<leader>aa` (default keybind for "Apply All" in sidekick.nvim) to accept all diffs. Alternatively, use `<leader>ac` to accept the current hunk or `<leader>ar` to reject it.

4. **Terminal Integration**: If you need to test the changes, open the built-in terminal with `<leader>at` and run:
   ```bash
   python -m pytest tests/test_utils.py -v
   ```
   The terminal buffers the output, so you can review test results without leaving Neovim.

5. **Chat with AI**: If you’re unsure about the refactor, open the chat interface with `<leader>ac` and ask:
   "Is this PEP 8 refactor correct? Should I add type hints?"
   The AI responds with:
   ```
   The refactor is correct for PEP 8. Adding type hints is optional but recommended for better code clarity. Example:
   ```python
   def __init__(self, input_data: list[str]) -> None:
   ```

After applying the changes, save the file with `:w` and continue coding seamlessly.