cli-snapshot-tester
Set up snapshot testing for CLI output with update workflows and diff reporting.
npx skills add a5c-ai/babysitter --skill cli-snapshot-tester --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CLI Snapshot Tester Set up snapshot testing for CLI output. ## Generated Patterns ```typescript import { execSync } from 'child_process'; import fs from 'fs'; import path from 'path'; export function runCliSnapshot(cmd: string, name: string): void { const output = execSync(cmd, { encoding: 'utf-8' }); const snapshotPath = path.join('__snapshots__', `${name}.txt`); if (process.env.UPDATE_SNAPSHOTS) { fs.mkdirSync(path.dirname(snapshotPath), { recursive: true }); fs.writeFileSync(snapshotPath, output); return; } const expected = fs.readFileSync(snapshotPath, 'utf-8'); expect(output).toBe(expected); } ``` ## Target Processes - cli-unit-integration-testing - cli-documentation-generation
- Generated Patterns
- Target Processes
What does the cli-snapshot-tester skill do?
Set up snapshot testing for CLI output with update workflows and diff reporting.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill cli-snapshot-tester --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.