smithery.ai

cli-testing

DRS CLI flag and command contract review checklist

First seen Mar 21, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,526 B
  • docs SUMMARY.md 51 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Purpose

Use this skill when reviewing changes in src/cli/** or command wiring in src/cli/index.ts. The goal is to catch CLI contract drift before release: broken flags, ambiguous defaults, and behavior changes that are not reflected in docs/tests.

DRS CLI Focus Areas

  • Validate flag definitions in src/cli/index.ts:

- long/short forms, defaults, required options, and env-var fallbacks. - mutually exclusive flags and precedence (--json + terminal output, --output paths, etc.).

  • Confirm command handlers in src/cli/*.ts honor declared flags:

- option names in commander wiring must map to runtime option fields. - staged/unstaged behavior, exit codes, and error paths should match help text.

  • Check operational consistency for workflow entrypoints:

- packaged review workflows (local-review, github-pr-review, gitlab-mr-review) should remain consistent. - JSON output mode should remain script-friendly and deterministic.

  • Validate docs/test coverage for CLI behavior changes:

- update README snippets when visible CLI behavior changes. - add or update tests for new flags, option interactions, and regressions.

Review Output Guidance

  • Prioritize issues affecting user-facing behavior, automation compatibility, and CI usage.
  • Flag missing integration coverage when a new/changed flag alters execution flow.
  • Do not report style-only nits unless they create ambiguity in CLI usage.