agent-ide-cli-fixture-test
Manual CLI testing and fixture verification workflow.
Install
mkdir -p .claude/skills/agent-ide-cli-fixture-test && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14797" && unzip -o skill.zip -d .claude/skills/agent-ide-cli-fixture-test && rm skill.zipInstalls to .claude/skills/agent-ide-cli-fixture-test
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Manual verification workflow for the agent-ide CLI against tests/fixtures. Use when asked to manually test CLI behavior, repeatedly mutate fixture projects, inspect git diff, restore fixtures between cases, cover multiple TS/JS cases, and fix any bug found during fixture-based CLI testing.Key capabilities
- →Manually test CLI behavior against fixture projects
- →Inspect git diff after CLI mutations
- →Restore fixtures between test cases
- →Cover multiple TypeScript/JavaScript CLI cases
- →Fix bugs found during fixture-based CLI testing
- →Validate mutated fixtures with TypeScript compiler or Node.js
How it works
This skill outlines a manual workflow to test the agent-ide CLI by running commands against fixture projects, inspecting git diffs, validating mutations, and restoring the fixture state.
Inputs & outputs
When to use agent-ide-cli-fixture-test
- →Verify CLI command mutation side effects
- →Test CLI find-references on a fixture
- →Run regression tests on CLI commands
- →Check CLI output consistency
About agent-ide-cli-fixture-test
Provides a systematic approach to build and test CLI commands against static fixture projects. It tracks mutations and validates state changes to ensure command correctness.
Manual verification workflow for the agent-ide CLI against tests/fixtures. Use when asked to manually test CLI behavior, repeatedly mutate fixture projects, inspect git diff, restore fixtures between cases, cover multiple TS/JS cases, and fix any bug found during fixture-based CLI testing.
When not to use it
- →The task does not involve manual verification of the agent-ide CLI.
- →The task does not require repeatedly mutating fixture projects.
- →The task does not involve inspecting git diff or restoring fixtures.
Limitations
- →The skill focuses on manual verification of the agent-ide CLI.
- →The skill does not automatically generate test cases.
- →The skill requires manual inspection of git diffs.
How it compares
This workflow provides a structured, manual testing approach for CLI tools using isolated fixture projects and explicit state validation, unlike ad-hoc testing that might miss side effects or fail to restore state.
Compared to similar skills
agent-ide-cli-fixture-test side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| agent-ide-cli-fixture-test (this skill) | 0 | 6mo | No flags | Intermediate |
| browser-tools | 6 | 1y | Review | Intermediate |
| playwright-mcp-dev | 5 | 5mo | No flags | Advanced |
| migrate | 1 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
browser-tools
Whamp
Lightweight Chrome automation toolkit with shared configuration, JSON-first output, and six focused scripts for starting, navigating, inspecting, capturing, evaluating, and cleaning up browser sessions.
playwright-mcp-dev
microsoft
Explains how to add and debug playwright MCP tools and CLI commands.
migrate
alirezarezvani
Migrate from Cypress or Selenium to Playwright. Use when user mentions "cypress", "selenium", "migrate tests", "convert tests", "switch to playwright", "move from cypress", or "replace selenium".
playwright-interactive
ComeOnOliver
Use a persistent `js_repl` Playwright session to debug local web or Electron apps, keep the same handles alive across iterations, and run functional plus visual QA without restarting the whole toolchain unless the process ownership changed.
e2e
AsiaOstrich
[UDS] 從 BDD 場景生成 E2E 測試骨架,支援框架偵測與覆蓋差距分析
e2e-testing
IntelligentLion
Design and implement end-to-end tests that validate complete user workflows across the full stack. Use when building browser automation, testing user journeys, cross-browser validation, visual regression testing, or verifying system behavior from the user perspective.