vidya381/devcheck

AI Summary: This issue proposes adding a check to ensure that Python packages installed in a virtual environment (venv) match the dependencies listed in the project's `requirements.txt` file. The goal is to detect outdated or missing packages within the venv and fail the process if discrepancies are found, enhancing dependency management.

AI Summary: This issue proposes adding a port reachability check for common services like Postgres, Redis, MySQL, and MongoDB. It requires attempting a TCP dial on localhost for their respective default ports and failing with a hint to start the service if nothing is listening. The implementation should be in `internal/check/port.go` and registered under relevant stack conditions.

AI Summary: This issue proposes adding a validation step for the `docker-compose.yml` file before other checks are performed. The goal is to catch syntax errors and typos early in the process, improving the reliability of the checker.

AI Summary: This issue proposes adding a Python version check to the project, similar to existing checks for Go and Node. The check should determine the required Python version from either a `.python-version` file (used by pyenv) or the `requires-python` field in `pyproject.toml`, and then compare it against the currently installed `python3 --version`.

AI Summary: This issue proposes adding a check to validate Go workspaces. When a `go.work` file is present, the system should verify that all modules listed in the `use` directive actually exist on disk and contain a `go.mod` file. This will help prevent build failures caused by missing local modules.

AI Summary: This issue proposes adding a new checker to a project that verifies the `.gitignore` file. The checker should ensure that common sensitive files and directories like `.env`, `node_modules/`, `__pycache__/`, and `*.log` are present in the `.gitignore`. If any are missing, the checker should issue a warning.

AI Summary: This issue proposes adding a check to verify if Git hooks are configured for Node.js (using Husky) and Python (using pre-commit). The checker should issue a warning if these hooks are missing, as they are beneficial but not strictly required.

AI Summary: This issue proposes adding a check to ensure that `golangci-lint` is installed and accessible in the PATH when a Go project is detected. This is important for CI pipelines that rely on this linter. The solution involves registering a pre-existing `BinaryCheck` within the Go stack configuration.

AI Summary: This issue requests adding basic connectivity checks for Postgres and Redis. If `DATABASE_URL` or `REDIS_URL` environment variables are set, the application should attempt to connect and ping Postgres using `pgx` or send a `PING` command to Redis using `go-redis`. The checks should reside in new `internal/checks` files.

AI Summary: This issue proposes adding a check to verify if a Python virtual environment (like .venv or venv) exists in the project root when Python is detected. If no virtual environment is found, the system should fail and provide a hint on how to create one.

AI Summary: This issue proposes adding new database connectivity checks for MySQL and MongoDB. The implementation involves creating new Go files for each database, registering them in the existing checker registry, and utilizing specific environment variables for connection strings.

AI Summary: This issue proposes adding a new checker to verify that all services defined in a Docker Compose file are running. The checker should execute `docker compose ps --format json` and report any stopped or missing services.

AI Summary: This issue proposes adding checks to a Go program to verify if project dependencies have been installed for Node, Python, and Go projects. The goal is to catch missing dependencies early in the development workflow, preventing users from encountering errors when trying to run the project.

AI Summary: This issue proposes adding a new check to ensure that all environment variable keys defined in `.env.example` are also present in the local `.env` file. The check should run when both files exist, and it should report any missing keys from `.env.example` in the `.env` file.

AI Summary: This issue involves adding binary checks for Go, Node.js, Python, and Java within the registry.go file. The task is to integrate the existing BinaryCheck functionality to verify the presence of specific executables (like `go`, `node`, `npm`, `python3`, `pip`, `java`, `mvn`, or `gradle`) on the system's PATH for each respective stack.

AI Summary: This issue proposes adding version checks for Go and Node.js installations. The Go check will read the version from `go.mod` and compare it to the installed Go version, while the Node.js check will look at `.nvmrc` or `engines.node` in `package.json` and compare it to the installed Node.js version. New Go files will be created for these checks and registered within the existing stack system.

AI Summary: This issue proposes adding two checks for Docker: verifying the `docker` binary is accessible in the system's PATH and confirming that the Docker daemon is actively running. The implementation involves modifying the `internal/checks/docker.go` file to include the daemon check and registering both checks within the `registry.go` file under the `stack.Docker` category.