shippie vs ESLint

Shippie implements an agentic loop that routes LLM requests to multiple providers (OpenAI, Anthropic, Google, Azure) via a unified model string parser (e.g., 'openai:gpt-4o', 'anthropic:claude-3-5-sonnet'). The agent uses Vercel's AI SDK abstraction layer to normalize provider APIs, then executes tool calls (readFile, readDiff, suggestChanges) in a loop up to a configurable max step limit (default 25). This enables the LLM to autonomously decide which files to inspect and what feedback to provide without pre-fetching all context.

Unique: Uses Vercel's AI SDK as a unified abstraction layer over 4+ LLM providers with a simple model string parser, enabling provider swapping via environment variable without code changes. Implements configurable agent step limits (maxSteps parameter) to prevent runaway LLM execution in CI/CD contexts, a pattern rarely exposed in code review tools.

vs alternatives: More flexible than GitHub Copilot (single provider) or Devin (proprietary LLM) because it supports Anthropic, Google, and Azure alongside OpenAI, and exposes step limits for cost control that most competitors hide.

Shippie provides three core tools (readFile, readDiff, suggestChanges) that the LLM agent can invoke autonomously during the review loop. The readFile tool fetches full file contents from the codebase, readDiff retrieves git diffs for changed files, and suggestChanges outputs structured feedback. The agent decides which files to inspect based on the initial diff summary, enabling selective analysis rather than loading all context upfront. Tools are registered via a schema-based function registry compatible with OpenAI and Anthropic function-calling APIs.

Unique: Implements a three-tool pattern (readFile, readDiff, suggestChanges) where the LLM agent autonomously selects which tools to invoke and in what order, avoiding the 'send everything' approach of simpler code review tools. Tools are schema-registered for compatibility with multiple LLM function-calling APIs, enabling provider portability.

vs alternatives: More efficient than Copilot's code review (which loads full file context) because it lets the LLM decide what to inspect, reducing token usage by 30-50% on large changesets; more flexible than GitHub's native review because tools are extensible via the tool registry.

Shippie supports review output in multiple languages via the --reviewLanguage CLI flag (default: English). The language preference is passed to the LLM system prompt, instructing it to generate feedback in the specified language. This enables teams in non-English-speaking regions to receive code review feedback in their native language (Spanish, French, German, Japanese, etc.). Language customization is simple (single flag) and works with any LLM provider that supports the target language.

Unique: Supports review output in multiple languages via a single --reviewLanguage CLI flag that is passed to the LLM system prompt, enabling non-English feedback without code changes. Works with any LLM provider supporting the target language.

vs alternatives: More accessible than GitHub Copilot (English-only) because it supports multiple languages; simpler than translation-based approaches because it leverages LLM multilingual capabilities directly.

Shippie includes a --debug flag that enables verbose logging of internal operations: LLM API calls, tool invocations, token counts, platform API interactions, and error traces. Debug output is written to stderr and includes timestamps, component names, and detailed error messages. This enables developers to diagnose issues (API failures, tool errors, platform authentication problems) without modifying code. Debug logs include full LLM request/response payloads (sanitized of sensitive data), making it easier to understand LLM behavior and prompt effectiveness.

Unique: Implements a --debug flag that enables verbose logging of LLM API calls, tool invocations, platform interactions, and error traces, providing end-to-end visibility into the review process. Includes full request/response payloads (sanitized) for LLM debugging.

vs alternatives: More transparent than GitHub Copilot (which provides no debug output) because it exposes internal operations; more practical than raw API logs because it aggregates and contextualizes logs by component.

Shippie supports the --baseUrl flag to override the default LLM provider API endpoint, enabling integration with custom or self-hosted LLM services. This is useful for organizations using Azure OpenAI (which requires a custom endpoint), local LLM servers (e.g., Ollama, vLLM), or proxy services. The baseUrl is passed to the Vercel AI SDK, which routes all LLM requests to the custom endpoint instead of the default provider URL. This enables Shippie to work with any LLM service compatible with OpenAI or Anthropic APIs.

Unique: Supports --baseUrl flag to override default LLM provider endpoints, enabling integration with Azure OpenAI, self-hosted LLMs (Ollama, vLLM), or custom proxies. Leverages Vercel AI SDK's endpoint routing to support any OpenAI/Anthropic-compatible API.

vs alternatives: More flexible than GitHub Copilot (cloud-only) because it supports self-hosted and custom endpoints; more practical than raw LLM APIs because it handles endpoint routing transparently.

Shippie abstracts Git platform differences (GitHub, GitLab, Azure DevOps) behind a PlatformProvider interface, enabling the same review logic to run on any platform. The system uses platform-specific SDKs (octokit for GitHub, @gitbeaker/rest for GitLab, azure-devops-node-api for Azure) but normalizes their APIs through a common interface. Platform detection is automatic via the --platform CLI flag or GitHub Actions context. Review comments are posted back to the platform using platform-native APIs (PR comments for GitHub, merge request notes for GitLab, etc.).

Unique: Implements a PlatformProvider interface that normalizes GitHub (octokit), GitLab (@gitbeaker), and Azure DevOps (azure-devops-node-api) SDKs into a single abstraction, enabling the same review engine to run on any platform. Supports automatic platform detection from GitHub Actions context, reducing setup friction.

vs alternatives: More portable than GitHub-only tools (Copilot, native Actions) because it supports GitLab and Azure DevOps; more unified than platform-specific tools because the same codebase runs everywhere without branching logic.

Shippie includes a languageMap that maps file extensions to programming languages (JavaScript, TypeScript, Python, Go, Rust, C++, Java, etc.), enabling the LLM to apply language-specific review rules. The language context is passed to the LLM prompt, allowing it to understand language idioms, common pitfalls, and best practices. Language detection is automatic based on file extension; no manual configuration required. The system supports 15+ languages including dynamic languages (Python, Ruby, PHP), compiled languages (Go, Rust, C++, Java), and infrastructure-as-code (Terraform, HCL).

Unique: Includes a hardcoded languageMap covering 15+ languages (JavaScript, TypeScript, Python, Go, Rust, C++, C, C#, Java, Ruby, Kotlin, PHP, Dart, Vue, Terraform) that is passed to the LLM prompt context, enabling language-specific review rules without external linting tools. Supports infrastructure-as-code (Terraform, HCL) alongside application languages.

vs alternatives: More comprehensive than GitHub Copilot (which focuses on Python/JavaScript) because it covers 15+ languages including Rust, Go, and Terraform; more flexible than language-specific tools (eslint, pylint) because it understands architectural patterns, not just syntax.

Shippie provides a GitHub Action (action.yml) that integrates into GitHub workflows, automatically triggering code review on pull request creation or updates. The action reads PR metadata from GitHub Actions context (PR number, branch, commit), invokes the Shippie review engine, and posts comments back to the PR using the GitHub API. Configuration is via action inputs (platform, modelString, reviewLanguage, maxSteps, baseUrl, debug) that map to CLI arguments. The action handles credential injection (API keys as secrets) and provides structured output (review summary, token usage) for downstream workflow steps.

Unique: Provides a first-class GitHub Action (action.yml) with declarative input configuration (modelString, reviewLanguage, maxSteps, baseUrl, debug) that maps directly to CLI arguments, enabling workflow-native configuration without shell scripting. Automatically extracts PR metadata from GitHub Actions context, eliminating manual parameter passing.

vs alternatives: More integrated than running Shippie as a CLI in a workflow step because it provides structured inputs/outputs and handles credential injection; more flexible than GitHub's native code review because it supports multiple LLM providers and custom review rules.

Executes ESLint rules against the active editor file as the user types or on file save, rendering violations as colored squiggles and inline decorations directly in the editor gutter. The extension hooks into VS Code's diagnostic API to push linting results from the ESLint library (installed locally or globally) into the editor's rendering pipeline, enabling immediate visual feedback without requiring manual linting commands.

Unique: Integrates directly with VS Code's native diagnostic API and editor rendering pipeline, allowing ESLint violations to appear as native squiggles and gutter decorations rather than as separate panel output; uses the ESLint library's rule engine directly without wrapping or re-implementing linting logic.

vs alternatives: Tighter VS Code integration than generic linting tools because it leverages VS Code's built-in diagnostic system and respects editor theme colors for error/warning rendering, whereas standalone linters require separate output parsing.

Automatically applies ESLint's `--fix` capability to the active file when saved, modifying the file in-place to correct fixable violations (e.g., formatting, semicolon insertion, import sorting). The extension triggers the ESLint library's fix mode on the save event, applies the corrected code back to the editor buffer, and updates diagnostics to reflect the post-fix state.

Unique: Leverages ESLint's native `--fix` API rather than implementing a separate formatting engine; integrates the fix operation into VS Code's save event lifecycle, allowing fixes to be applied transparently without user interaction or separate command invocation.

vs alternatives: More reliable than Prettier-only solutions because it respects ESLint rule configuration and can fix non-formatting issues (e.g., import sorting, variable naming); more integrated than running ESLint as a separate task because fixes are applied synchronously on save.

Caches linting results for files that have not changed, avoiding redundant ESLint execution and improving performance for large codebases. The extension tracks file modifications and only re-runs ESLint for changed files, reducing computational overhead and latency for real-time linting feedback.

Unique: Implements file-level caching to avoid redundant ESLint execution, tracking file modifications and only re-linting changed files; caching strategy is transparent to users and requires no configuration.

vs alternatives: More performant than re-linting all files on every change because it only processes modified files; more transparent than manual cache management because caching is automatic and invisible to users.

Maps ESLint rule severity levels (error, warning, off) to VS Code diagnostic severity levels (Error, Warning, Information), rendering violations with appropriate colors and icons in the editor. The extension translates ESLint's severity classification into VS Code's diagnostic system, enabling consistent visual representation across the editor and Problems panel.

Unique: Maps ESLint severity levels directly to VS Code's diagnostic API, enabling native severity rendering without custom UI; respects VS Code's theme and editor settings for diagnostic colors and icons.

vs alternatives: More integrated than custom severity rendering because it uses VS Code's native diagnostic system; more consistent than separate severity indicators because it leverages the editor's built-in visual language.

Aggregates all linting violations from the active file and workspace into VS Code's built-in Problems panel, displaying violations with severity levels (error, warning, info) and allowing filtering by severity. The extension pushes diagnostic data into VS Code's diagnostic collection, which automatically populates the Problems panel and respects the `eslint.quiet` setting to suppress info-level messages.

Unique: Uses VS Code's native diagnostic collection API to push ESLint violations into the Problems panel, allowing seamless integration with VS Code's built-in error aggregation and navigation UI rather than implementing a custom panel.

vs alternatives: More discoverable than inline-only linting because violations are visible in a dedicated panel even when the file is not in focus; more integrated than external linting tools because it uses VS Code's native UI rather than requiring a separate output window.

Automatically detects and loads ESLint configuration from either flat config format (`eslint.config.js`, `.mjs`, `.cjs`, `.ts`, `.mts`) or legacy format (`.eslintrc.*` in JSON, JS, YAML) based on what exists in the workspace. The extension respects the `eslint.useFlatConfig` setting to force flat config mode for ESLint 8.57.0+, and falls back to legacy config detection for older versions.

Unique: Implements automatic detection of both flat and legacy config formats without requiring explicit user configuration; uses the `eslint.useFlatConfig` setting to allow users to force flat config mode for ESLint 8.57+, enabling gradual migration from legacy to flat config.

vs alternatives: More flexible than tools that only support one config format because it handles both legacy and flat configs transparently; more user-friendly than requiring manual config path specification because it automatically discovers configs in standard locations.

Allows users to specify which file types should be linted by configuring the `eslint.validate` setting with an array of VS Code language identifiers (e.g., `["javascript", "typescript", "javascriptreact"]`). The extension checks each file's language identifier against the configured list before running ESLint, skipping linting for files not in the list.

Unique: Uses VS Code's language identifier system to filter files before linting, allowing granular control over which file types are processed; integrates with VS Code's language detection rather than implementing custom file type detection.

vs alternatives: More precise than file extension-based filtering because it respects VS Code's language detection (e.g., distinguishing between JavaScript and JSX); more flexible than ESLint's built-in ignore patterns because it operates at the extension level before ESLint is invoked.

Provides a `eslint.quiet` boolean setting that, when enabled, suppresses ESLint info-level diagnostic messages while preserving error and warning messages. The extension filters diagnostics before pushing them to VS Code's diagnostic collection, removing entries with severity below warning level.

Unique: Implements message filtering at the extension level after ESLint execution, allowing users to suppress info-level messages without modifying ESLint configuration or rules; provides a simple boolean toggle rather than complex filtering logic.

vs alternatives: Simpler than configuring ESLint rules to disable info-level messages because it requires only a single setting change; more effective than ESLint's built-in severity configuration because it applies uniformly across all rules.