Commit Helper MCP

# Requirements Analysis: Security-Focused Repository Operations ## Problem Statement The current Commit Helper MCP design allows operations on arbitrary filesystem locations through explicit repository path parameters and environment variables. This creates significant security risks: 1. **Security Vulnerability**: Services can operate on any accessible directory in the filesystem 2. **Path Traversal Risk**: Potential for accessing sensitive directories 3. **Complex Path Resolution**: Multiple sources of truth for repository location 4. **Inconsistent Behavior**: Different tools may resolve paths differently ## Security Requirements From a security perspective, the solution must: 1. **Restrict Operations**: Only allow operations on the current working directory 2. **Eliminate Parameters**: Remove all `repo_path` parameters from tools 3. **Remove Environment Variables**: Eliminate `COMMITIZEN_REPO_PATH` and similar 4. **Prevent Path Traversal**: Make it impossible to access other directories ## User Requirements From a user perspective, the solution should: 1. **Be Predictable**: Always operate on the current directory 2. **Be Explicit**: Require users to navigate to target directory 3. **Provide Clear Errors**: Give helpful messages when not in valid repository 4. **Support Workflows**: Enable multi-repository work through directory changes ## Technical Requirements From a technical perspective, the solution must: 1. **Simplify Architecture**: Remove all path resolution logic 2. **Use CWD Only**: All operations use `os.getcwd()` 3. **Validate CWD**: Check current directory is valid before operations 4. **Handle Errors**: Provide clear error messages for invalid directories 5. **Support Testing**: Allow testing without complex path mocking ## Integration Requirements The solution must integrate with: 1. **Existing MCP Tools**: Update all tools to remove path parameters 2. **Error Handling System**: Use existing error response infrastructure 3. **Service Layer**: Update services to only use CWD 4. **Testing Framework**: Simplify tests to work with CWD ## Success Criteria The solution will be successful if it: 1. Eliminates all repository path parameters from tools 2. Removes all environment variable dependencies 3. Restricts all operations to current working directory 4. Simplifies the codebase significantly 5. Provides clear migration path for users