Test CLI
Test CLIs across arguments, streams, exit codes, files, environment, signals, and interaction.
Install
npx skills add sandbaseai/workbuddy-skill --skill test-cligit clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/test-cli ~/.claude/skills/test-cliPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test CLI Verify the CLI contract from a user's perspective, including behavior that is easy to miss when only calling internal functions. Use this Skill for new commands, regression testing, packaging checks, release readiness, or diagnosis of shell- and platform-specific failures. ## Establish the contract Identify the exact installed artifact, version, entry point, supported operating systems, shell assumptions, and documented command behavior. Record: - commands, subcommands, arguments, defaults, aliases, and incompatible options - configuration files, environment variables, and precedence rules - stdin formats and stdout/stderr contracts - exit codes, files, network calls, and other observable side effects - interactive prompts, TTY requirements, signals, and cancellation semantics Test the built or installed artifact when release behavior matters; running a source module directly may bypass packaging, launchers, or bundled resources. ## WorkBuddy test workflow 1. Create an isolated temporary directory with disposable fixtures. Set an explicit working directory and only the environment variables needed by the scenario. 2. Check help, version, unknown-command, and no-argument behavior before a minimal successful invocation. 3. Exercise required, optional, repeated, mutually exclusive, and ordered arguments. Include spaces, quotes, glob-like characters, Unicode, empty values, leading hyphens, long paths, and platform path separators where
Details
- Skill name
test-cli- Repository
- sandbaseai/workbuddy-skill
- Path
skills/test-cli/SKILL.md- License
- MIT
- Repo updated
- 8 September 2026
FAQ
What does the Test CLI skill do?
Test CLIs across arguments, streams, exit codes, files, environment, signals, and interaction.
How do I install the Test CLI skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill test-cli. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test CLI popular?
It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.
Related skills
Access Control Security Best Practices
9sandbaseai/workbuddy-skill
Design, review, implement, and verify least-privilege access controls across users, services, tenants, resources, and administrative workflows.
Accessibility Review
9sandbaseai/workbuddy-skill
Use when reviewing a web interface or interaction for semantic, keyboard, focus, screen-reader, ARIA, and contrast accessibility risks.
Acquire Codebase Knowledge
9sandbaseai/workbuddy-skill
Use when the user asks to map, document, or onboard into an existing codebase and needs evidence-backed architecture, structure, conventions, integrations, testing, and concerns documentation.
Test Driven Development
9sandbaseai/workbuddy-skill
Use when implementing a feature, bug fix, refactor, or behavior change and a regression-safe test-first workflow is appropriate.
Test Analyzer
5euxx/claude-skills-for-copilot
Reviews test coverage quality from a behavioral perspective, identifying critical gaps and test quality issues. Does not check line coverage — checks meaningful scenario coverage. Use after adding or modifying tests.
Test Runner
9sandbaseai/workbuddy-skill
Use when running repository tests and reporting concise, reproducible results in fast or full mode.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.