testing-test-writing
Imported from https://github.com/mshafei721/Turbocat.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install mshafei721-turbocat-testing-test-writing
Repository
Skill path: .claude/skills/testing-test-writing
Imported from https://github.com/mshafei721/Turbocat.
Open repositoryBest for
Primary workflow: Write Technical Docs.
Technical facets: Full Stack, Tech Writer, Testing.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: mshafei721.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install testing-test-writing into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/mshafei721/Turbocat before adding testing-test-writing to shared team environments
- Use testing-test-writing for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: Testing Test Writing description: Write focused, strategic tests for core user flows with behavior-based testing, clear naming, and proper mocking of external dependencies. Use this skill when writing unit tests, integration tests, or end-to-end tests. When working on files in tests/, __tests__/, spec/, or *.test.ts, *.spec.ts files. When deciding what to test during feature development. When naming test cases descriptively. When mocking databases, APIs, or external services. When focusing on testing behavior rather than implementation details. --- ## When to use this skill: - When writing new unit, integration, or e2e tests - When modifying existing test files - When working on files in tests/, __tests__/, spec/, or test/ directories - When working on files like *.test.ts, *.spec.ts, *_test.py, *_spec.rb - When deciding what code to test during feature development - When choosing to test core user flows vs. edge cases - When writing descriptive test names that explain expected outcomes - When mocking databases, external APIs, or file systems - When isolating units under test from dependencies - When ensuring tests focus on behavior, not implementation - When reviewing test code for clarity and maintainability - When keeping test execution fast for developer feedback # Testing Test Writing This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle testing test writing. ## Instructions For details, refer to the information provided in this file: [testing test writing](../../../agent-os/standards/testing/test-writing.md)