How bugsterapp/bugster-cli works
Project type and purpose
• This is a Python-based command-line interface (“Bugster CLI”) that analyzes local projects, detects frameworks, gathers Git metadata, and communicates with the Bugster backend (via REST/WebSocket) to report or retrieve information.
• The README confirms it’s a CLI tool intended for installation via script or pip, having commands like “analyze”, “login”, “init”, etc.
File structure
• Top-level files/directories:
• bugster/ ← main package
• scripts/ ← helper install/build scripts
• .github/workflows ← CI/CD pipelines
• setup.py, pyproject.toml, requirements.txt ← packaging/config
• Inside bugster/:
• cli.py ← entrypoint defining CLI interface
• commands/ ← command handlers (analyze, login, init, test, middleware)
• analyzer/ ← core analysis engine, subdivided into framework_detector & app_analyzer
• clients/ ← modules for communicating with external services (mcp_client, ws_client)
• libs/ ← internal services (test_cases_service), settings, enums, errors
• utils/ ← file I/O, Git info, user config helpers
• constants.py, types.py ← shared definitions
README for additional insights
• “bugster analyze” presumably invokes analyzer → clients → remote API.