Dave-London/Pare

AI Summary: This GitHub issue proposes adding `oxlint` as a new linting tool to the `@paretools/lint` package. The feature requires implementing a wrapper that executes `oxlint` with JSON output, parses this output into a defined schema, and integrates it following the existing ESLint tool pattern, including Zod schema validation and comprehensive tests.

AI Summary: This issue proposes adding a `stylelint` tool to the `@paretools/lint` package. The task involves wrapping the `stylelint` command to output JSON, defining a Zod schema for its output, implementing parsing and formatting logic, and integrating it into the existing linting framework following the pattern established by the ESLint tool.

AI Summary: This GitHub issue proposes adding an `update` tool to `@paretools/cargo` that wraps the native `cargo update` command. The tool should support an optional package name argument and parse the `cargo update` output into a structured JSON schema, including success status, raw output, and an optional count of updated packages. Implementation involves creating Zod schemas, parsers, and tests, while following existing patterns and ensuring security against flag injection.

AI Summary: This GitHub issue proposes adding a `search` tool to `@paretools/npm`. The tool will wrap the `npm search <query> --json` command, parsing its native JSON output into a specified schema. Key implementation tasks include creating Zod schemas, parsers, formatters, and ensuring security against flag injection in the query.

AI Summary: This GitHub issue proposes adding an `info` tool to `@paretools/npm` that wraps the `npm info package --json` command. The new tool will output native JSON data conforming to a specified TypeScript schema, including package name, version, description, and distribution details. Implementation involves creating a Zod schema, parser, formatter, and ensuring security against flag injection by following an existing pattern.

AI Summary: This GitHub issue proposes adding a new `ruff-format` tool to the `@paretools/python` package, designed to wrap the `ruff format` command. The implementation should closely follow the pattern of the existing `black` tool, supporting an optional `--check` flag and accepting file paths. It includes a defined output schema for reporting success and files changed, along with a checklist of necessary development steps.

AI Summary: This issue proposes adding a `pip-show` tool to `@paretools/python` that wraps the `pip show package-name` command. The tool will parse the command's key-value output into a structured JSON schema, including fields like name, version, and requirements. Implementation involves creating a Zod schema, parser, formatter, tool registration, and ensuring security against flag injection.

AI Summary: This GitHub issue proposes adding a new `get` tool to the `@paretools/go` package. This tool will wrap the `go get package@version` command, providing a structured output schema including success status, package, and optional version or raw output. Implementation involves creating a Zod schema, parser, formatter, tool registration, comprehensive tests, and ensuring robust flag injection prevention.

AI Summary: This GitHub issue proposes adding a new `pip-list` tool to the `@paretools/python` package. The tool will execute `pip list --format json` and parse its output into a structured format, including a list of packages with their names and versions, and a total count, following an existing tool pattern.

AI Summary: This issue proposes adding a new `list` tool to the `@paretools/go` package. The tool will execute `go list -json ./...`, parse its JSONL output by splitting on `}\n{`, and transform it into a structured TypeScript object conforming to a defined schema. Implementation involves creating a Zod schema, parser, formatter, tool file, registration, and comprehensive tests, following existing Go tool patterns.

AI Summary: This issue proposes adding an `env` tool to `@paretools/go` that wraps the `go env -json` command. The tool will parse the native JSON output, validate it against a defined TypeScript schema using Zod, and then format it. The task involves creating the Zod schema, parser, formatter, tool file, registration, and comprehensive tests, following an existing pattern.

AI Summary: This feature request proposes adding a new `compose-ps` tool to the `@paretools/docker` package. The tool will execute `docker compose ps --format json` and parse its output into a specified TypeScript schema, following existing patterns for other Docker Compose tools and including Zod schema validation and tests.

AI Summary: This issue proposes adding a new `volume-ls` tool to the `@paretools/docker` package. The tool will wrap the `docker volume ls --format json` command, providing a structured JSON output containing volume details (name, driver, mountpoint, scope) and a total count. The implementation should follow existing patterns for other docker tools, including Zod schema definition, parsing, formatting, tool registration, and tests.

AI Summary: This issue proposes adding an `inspect` tool to the `@paretools/docker` package, which will wrap the `docker inspect --format json` command. The tool will parse the native JSON output into a specified TypeScript schema, following the existing pattern established by the `ps.ts` tool. Implementation involves creating new schema, parser, formatter, and tool files, along with tests.

AI Summary: This issue proposes adding a new `remote` tool to the `@paretools/git` package. The tool will execute `git remote -v`, parse its output to group fetch and push URLs by remote name, and present the data in a structured JSON format. Implementation involves creating a new tool file, a parser, a formatter, updating schemas, and adding tests, following an existing tool pattern.

AI Summary: This issue proposes adding a new `tag` tool to the `@paretools/git` package. This tool will execute a specific `git tag` command to list tags and parse its tab-separated output into a structured JSON format, including tag name, date, and message. The implementation should follow the existing pattern of the `status` tool, involving new schema, parser, formatter, and tool files, along with corresponding tests.

AI Summary: This issue requests the creation of a `CONTRIBUTING.md` file to guide new contributors. The file should detail prerequisites, development setup steps, project structure, how to add new tools, testing procedures, code style, and the pull request process, leveraging existing project information.