chore: update agent communication guidelines and Python development instructions for clarity and consistency for github copilot

Author: d-biehl

.github/copilot-instructions.md

@@ -23,45 +23,18 @@ RobotCode is a comprehensive Robot Framework toolkit that provides IDE extension
 
 ## Agent Communication Guidelines
 
-### When to Ask vs. Implement Directly
+### Core Rules
 
-- **ALWAYS ASK when multiple valid approaches exist:** Present specific options and wait for user choice
-- **ALWAYS ASK when requirements are incomplete:** Don't make assumptions about missing details
-- **IMPLEMENT DIRECTLY only when:** Requirements are clear and there's one obvious correct approach
-- **STOP and ASK if unsure:** Better to ask than to implement the wrong solution
+- **REVIEW/ANALYZE/CHECK/EXAMINE:** READ-ONLY operations. Provide analysis and feedback, NEVER make changes
+- **IMPLEMENT/ADD/CREATE/FIX/CHANGE:** Implementation required. Ask for clarification if multiple approaches exist
+- **IMPROVE/OPTIMIZE/REFACTOR:** Always ask for specific approach before implementing
 
-### Question Format Rules
+### Communication Flow
 
-- **Wait for Response:** NEVER implement after asking - always wait for the user's explicit choice
-- **Specific Options:** Provide concrete alternatives, not vague descriptions
-- **Number Options:** Use "1), 2), 3)" format for easy selection
-- **Always Include "Other":** End with "4) Other approach - please describe what you have in mind"
-- **One Question at a Time:** Ask one focused question, get answer, then proceed or ask next question
-
-### Implementation Flow
-
-1. **Analyze Request:** Is this clear and unambiguous?
-2. **If Unclear:** Ask specific question with numbered options and STOP
-3. **Wait for Answer:** Do not proceed until user responds
-4. **Confirm Understanding:** "I understand you want option X. I'll implement..."
-5. **Then Implement:** Only after explicit user choice
-
-### Example Interaction Pattern
-
-```
-User: "Add error handling to the function"
-
-Agent: "I see several approaches for error handling. Which would you prefer?
-
-1) Try-catch blocks with specific exception types
-2) Return Result<T, Error> pattern with error types
-3) Simple boolean return with logging
-4) Other approach - please describe what you have in mind
-
-Please let me know which option you'd like me to implement."
-
-[WAIT FOR USER RESPONSE - DO NOT IMPLEMENT YET]
-```
+1. **Recognize Intent:** Review request vs. Implementation request?
+2. **For Reviews:** Analyze and suggest, but don't change anything
+3. **For Implementation:** Ask numbered options if unclear, wait for response, then implement
+4. **Question Format:** Use "A), B), C), D), ..." format, always end with "Other approach"
 
 ## Tech Stack
 

.github/instructions/python-development.instructions.md

@@ -28,83 +28,39 @@ applyTo: **/*.py
 - **MUST** use proper __init__.py files for package imports
 
 ### Code Style Standards
-- **Formatting:** Follow Black code style with line length 88
-- **Imports:** isort with profile=black
-- **Type Hints:** Required for all public APIs
+- **Formatting:** we use ruff for formatting
+- **Type Hints:** Required for all APIs
 - **Docstrings:** Google style for modules, classes, and functions
+- **linting:** use ruff for static analysis and mypy for type checking
 
-### Environment Setup
-```bash
-hatch run install-packages    # Install all packages in development mode
-```
-
-### Testing Commands
-```bash
-hatch run test.rf70:test      # Test with Robot Framework 7.0
-hatch run test.rf70.py311:test # Specific Python + RF combination
-hatch run cov                 # Run with coverage reporting
-pytest --regtest2-reset      # Update test snapshots
-```
 
 ### Code Quality
 ```bash
 hatch run lint:all            # All linting checks (black, isort, flake8)
 hatch run lint:fix            # Auto-fix style issues
 ```
 
-## CLI Error Handling Pattern
-
-**REQUIRED** pattern for all CLI tools:
-```python
-try:
-  result = execute_command()
-except Exception as e:
-  app.error(f"Failed to execute: {e}")
-```
-
-## Package-Specific Guidelines
-
-### Core Package (`packages/core/`)
-- **Base utilities and shared functionality**
-- **MUST** be importable by all other packages
-- **NO** dependencies on other RobotCode packages
-
-### Language Server (`packages/language_server/`)
-- **LSP implementation for IDE integration**
-- **ALWAYS** use asyncio patterns
-- **REQUIRED** proper error isolation per workspace
-
-### Debugger (`packages/debugger/`)
-- **Debug Adapter Protocol implementation**
-- **MUST** handle multi-workspace scenarios
-- **REQUIRED** proper session management
-
-### Runner (`packages/runner/`)
-- **Enhanced Robot Framework execution tools**
-- **ALWAYS** use Robot Framework native parser
-- **REQUIRED** configuration via robot.toml
-
 ### Testing Requirements
 
+### Python Interpreter
+- **ask your tools** wich python interpreter to use for the project/workspace
+
 ### Matrix Testing
 - **COMPREHENSIVE** testing across Python 3.8-3.13
 - **MATRIX** testing with Robot Framework 5.0-7.3
 - **INTEGRATION** tests in tests/robotcode/ with real scenarios
 - **SNAPSHOT** testing with pytest regtest2
 
 ### Test Execution
+
+**IMPORTANT**use the correct Python environment selected in your IDE
+
+- **USE** `pytest .` to run unit tests,
 - **USE** `pytest --regtest2-reset` to update snapshots
 - **RUN** specific environments: `hatch run test.rf70.py311:test`
 - **COVERAGE** reporting with `hatch run cov`
 
-## Configuration System
-
-### robot.toml Configuration
-- **IMPLEMENT** robot.toml parsing throughout CLI and language server
-- **SUPPORT** profile management and inheritance
-- **VALIDATE** configuration options
-
-### Multi-Platform Consistency
+## Multi-Platform Consistency
 - **ENSURE** consistent behavior across VS Code and IntelliJ
 - **MAINTAIN** unified configuration approach
 - **DOCUMENT** platform-specific differences

hatch.toml

@@ -142,6 +142,7 @@ features = ["all"]
 typing = "mypy --no-incremental --cache-dir /dev/null {args:.}"
 style = ["ruff check .", "ruff format --diff ."]
 all = ["style", "typing"]
+fix = ["ruff check --fix .", "ruff format ."]
 
 [envs.lint.overrides]
 platform.windows.scripts = [