unit-test-philosophyRisk-based unit testing and Allure-readable behavioral spec style for open-agreements. Use when user says "add tests," "test quality," "coverage expansion,"...
Install via ClawdBot CLI:
clawdbot install stevenobiajulu/unit-test-philosophyGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 8, 2026
A developer modifies the contract patch logic in src/core and needs to ensure mutating flows cannot corrupt legal output. The skill guides ranking tests by blast radius and prioritizing validation, transactional guarantees, and no-partial-mutation checks. This prevents regressions that could produce incorrect legal documents in production.
A QA engineer wants readable behavior documentation embedded directly in unit and integration tests rather than a separate test type. The skill defines Given/When/Then step conventions, helper usage from allure-test.ts, and attachment practices for debugging. This keeps specs and tests coextensive and traceable to OpenSpec scenario IDs.
A team maintaining packages/contracts-workspace notices branch-heavy validation code with low coverage. The skill provides a ranked workflow: validation/error branches first, strict vs permissive behavior, then invariants like idempotency. Tests are added with severity labels reflecting failure impact.
When adding important new behavior, engineers need tests mapped to canonical or active change-package scenario IDs via .openspec('OA-###'). The skill explains mapping tests to active change packages first and promoting IDs when archiving. This preserves stable traceability from spec to test.
A repository contains older *.allure.test.ts files that split test types unnecessarily. The skill mandates collocated src/<module>.test.ts files with Allure style inline and a gradual migration policy. It also warns against raw allure-vitest imports in favor of repo helpers.
An engineering organization adopts the skill to standardize testing philosophy across teams working on legal automation tooling. By embedding Allure style and risk-based coverage into normal test files, teams reduce review friction and prevent regressions. The skill provides shared conventions without requiring new tooling purchases.
Maintainers of an open-source legal agreements library use scenario IDs and behavioral specs to keep contributions consistent and auditable. Contributors follow the coverage expansion workflow, raising the quality bar for community pull requests. Traceability to OpenSpec scenarios builds trust with adopters.
A CLM vendor uses the skill to harden mutation correctness and legal-output integrity, which are directly tied to customer trust and audit requirements. Severity rubrics map critical guardrails to failure impact, guiding where to invest test effort. Allure reports with attached before/after document state support internal and external audits.
💬 Integration Tip
Wire the command checklist into CI so test:run, test:coverage, check:spec-coverage, and check:allure-labels gate merges, and use repo allure-test.ts helpers exclusively to keep labels and attachments consistent across src and integration-tests.
Scored Oct 8, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.