Back to skills
SkillHub ClubWrite Technical DocsFull StackTech WriterTesting
testing-test-writing
Imported from https://github.com/DevanB/lucidlog.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Stars
0
Hot score
74
Updated
March 20, 2026
Overall rating
C2.0
Composite score
2.0
Best-practice grade
C57.6
Install command
npx @skill-hub/cli install devanb-lucidlog-testing-test-writing
Repository
DevanB/lucidlog
Skill path: .claude/skills/testing-test-writing
Imported from https://github.com/DevanB/lucidlog.
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: DevanB.
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/DevanB/lucidlog before adding testing-test-writing to shared team environments
- Use testing-test-writing for development workflows
Works across
Claude CodeCodex CLIGemini CLIOpenCode
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: Testing Test Writing description: Write focused tests for core user flows and critical paths using Pest framework, with minimal tests during development and strategic coverage at completion points. Use this skill when creating or editing test files in tests/Feature/ or tests/Unit/ directories, when writing Pest tests with descriptive names, when testing critical user workflows and business logic, when mocking external dependencies, when implementing fast unit tests, when testing behavior rather than implementation details, or when deciding what needs test coverage at feature completion. --- # 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. ## When to use this skill - When creating new test files in `tests/Feature/` or `tests/Unit/` directories - When writing Pest tests with descriptive, clear test names - When testing core user workflows and critical business paths - When deciding what needs test coverage at feature completion points - When mocking external dependencies (databases, APIs, file systems, services) - When writing fast-executing unit tests - When focusing tests on behavior and outcomes rather than implementation details - When using Pest datasets to handle multiple test scenarios efficiently - When testing validation rules, business logic, or API endpoints - When implementing integration tests for critical features - When running tests before committing code changes - When skipping tests for non-critical utilities or edge cases (until explicitly required) ## Instructions For details, refer to the information provided in this file: [testing test writing](../../../agent-os/standards/testing/test-writing.md)