Menu
Use when adding or updating unit tests for create-vibe-start CLI modules, especially Vitest tests that must isolate prompts, shell commands, platform detection, and package imports from real external resources.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Reduce an existing Codex skill to its minimum useful form, extract on-demand context into linked sibling files, or decide that the skill should be deleted. Use when the user asks to diet, slim, trim, simplify, minimize, reevaluate, or remove bloat from a skill while preserving its trigger behavior, tone, safety constraints, and practical usefulness.
Create a GitHub pull request from the current branch—commit uncommitted changes, push, and open a PR against main with an auto-generated title and Summary/Testing body sections.
Review code for correctness risks, maintainability, security, and lifecycle issues with severity-tagged findings.
Update an existing GitHub pull request for the current branch—commit and push latest changes, then refresh the PR title and body from the full diff against main.
Interview the user with Socratic questions to turn an ambiguous request into actionable requirements. Use when the user asks for a deep-interview, requirement clarification, or help organizing their thoughts, or when the goal, scope, constraints, or definition of done are unclear. Do not use when the request is already concrete, or for low-value work like typo fixes, small config tweaks, or test top-ups.
Use when creating or updating project-specific Codex skills for create-vibe-start, especially skills stored under .agents/skills with concise SKILL.md instructions and progressively loaded reference files.
| name | unit-test |
| description | Use when adding or updating unit tests for create-vibe-start CLI modules, especially Vitest tests that must isolate prompts, shell commands, platform detection, and package imports from real external resources. |
gh, vercel, codex, package managers, login flows, and network requests with mocks in unit tests.__tests__ folder next to the file under test..spec.ts suffix. Example: foo.ts -> __tests__/foo.spec.ts.__tests__ folder.vi.mock(...) before importing the module under test when the module reads mocked imports at load time.vi.spyOn(...) for mocking runtime values; do not directly rewrite globals with Object.defineProperty(...) unless no test helper can model the behavior.await import(...) after mocks for step configuration tests.vi.resetModules() when testing environment-sensitive modules.