* feat: add missing install.sh script referenced in README\n\n- Create comprehensive installation script with POSIX compatibility\n- Add interactive and non-interactive installation modes\n- Include prerequisites checking and MCP server setup guidance\n- Replace echo -e with printf for better POSIX compliance
* fix: resolve linting errors in install_mcp.py and clean_command_names.py
Fix multiple ruff linting errors to ensure CI/CD pipeline passes:
- install_mcp.py: Remove unused pathlib.Path import, replace bare except
with specific exception types (ValueError, IndexError), remove
extraneous f-string prefixes on lines without placeholders
- clean_command_names.py: Remove unused os import, convert f-strings
without placeholders to regular strings
- pyproject.toml: Exclude docs/ directory from ruff checks to avoid
N999 module naming violations in documentation templates
All linting checks now pass successfully.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* style: apply ruff format to Python source files
Apply ruff formatting rules to CLI and scripts modules to ensure
consistent code style across the codebase.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* fix(ci): remove incompatible pip cache from quick-check workflow
## Problem
GitHub Actions was failing with error:
"Cache folder path is retrieved for pip but doesn't exist on disk:
/home/runner/.cache/pip. This likely indicates that there are no
dependencies to cache."
## Root Cause
The quick-check.yml workflow specified `cache: 'pip'` in the Python
setup step, but the workflow uses UV (not pip) for package management
via `uv pip install --system -e ".[dev]"`.
UV uses its own cache directory (~/.cache/uv), so the pip cache path
was never created, causing the error.
This was a migration oversight:
- When UV was adopted as the project standard (commit 00706f0), the
CLAUDE.md established "CRITICAL: Never use pip directly" rule
- The test.yml workflow was created correctly without pip cache
- The quick-check.yml workflow incorrectly included pip cache from
initial creation (commit 8c0559c) and was not updated during migration
## Solution
Remove `cache: 'pip'` line to align with:
- Project's UV-first architecture (CLAUDE.md)
- test.yml workflow (which runs successfully without pip cache)
- readme-quality-check.yml workflow (no cache needed)
Note: publish-pypi.yml intentionally uses pip cache as it directly
runs `python -m pip install` commands, which is correct for that workflow.
## Impact
- ✅ Eliminates GitHub Actions cache warning
- ✅ Aligns all UV-based workflows consistently
- ✅ Follows project standards documented in CLAUDE.md
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
Changed from 'uv run <command>' to direct '<command>' execution
since we're using 'uv pip install --system' which installs to
the system Python environment.
This fixes pytest-cov and other plugin detection issues.
Changes:
- pytest instead of uv run pytest
- ruff instead of uv run ruff
- superclaude instead of uv run superclaude
- Added uv pip list for debugging
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Added --system flag to all uv pip install commands to fix
"No virtual environment found" error in GitHub Actions CI/CD.
UV requires either a virtual environment or the --system flag
in CI/CD environments.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
