Conversation
Replace hardcoded Python-specific setup with flexible YAML-based configuration system that supports multiple development environments. Users can now define custom environments with specific agents, MCP servers, hooks, and commands. Key changes: - Rename setup-python-environment scripts to setup-environment - Add YAML parser for configuration files without external dependencies - Support dynamic command registration (claude-python, claude-fullstack, etc.) - Enable MCP server configuration for all transport types (HTTP, SSE, stdio) - Implement hooks management with automatic settings.json updates - Create example configurations for Python, full-stack, and business analyst environments - Add comprehensive documentation for environment configurations
Fixed PowerShell command syntax throughout documentation to properly set environment variables. Updated all READMEs to reflect new configuration-driven setup system. Added hooks directory documentation and improved YAML parser robustness. Key changes: - Fix PowerShell command syntax to use proper wrapper for environment variables - Update scripts/README.md for configuration-driven environment setup - Remove references to deleted full-stack.yaml and business-analyst.yaml configs - Create environments/templates/basic-template.yaml for custom configurations - Add comprehensive hooks/README.md documentation - Fix setup-environment.py to install Claude Code before dependencies - Improve parse_yaml() to handle tabs and edge cases better - Add hooks directory to main() setup flow - Fix python.yaml indentation (tabs to spaces) - Add executable permission to python_ruff_lint.py hook
Fixed PowerShell escaping issues that caused '$env:CLAUDE_ENV_CONFIG' to be evaluated incorrectly. Added multiple command options for Windows users with clear documentation. Improved error messages for missing configuration files. Key changes: - Fix PowerShell variable escaping with backtick in one-liner commands - Add simple two-step approach as recommended option for Windows users - Improve error handling for 404 errors when configuration file not found - Add informative messages about available configurations - Update bootstrap script to show which configuration is being used - Fix Markdown heading syntax to avoid linting errors - Add proper exception chaining with 'from None' - Remove duplicate import of HTTPError
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.