doompi-testing
/doompi-testing
Design, add, and run focused tests for repository behavior. Use for test implementation, regression coverage, verification, or diagnosing a failing test, not for a review-only request.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Design, add, and run focused tests for repository behavior. Use for test implementation, regression coverage, verification, or diagnosing a failing test, not for a review-only request.
Original author description
Design, add, and run focused tests for repository behavior. Use for test implementation, regression coverage, verification, or diagnosing a failing test, not for a review-only request.
How it works
- Test design
- Test implementation
- Evidence
SKILL.md preview
--- name: doompi-testing description: Design, add, and run focused tests for repository behavior. Use for test implementation, regression coverage, verification, or diagnosing a failing test, not for a review-only request. --- # Focused Testing Produce evidence about observable behavior, not coverage for its own sake. ## Test design - Read repository instructions and existing tests before selecting tools or commands. - Translate the request into success, failure, boundary, and regression cases. - Prefer the lowest-cost test level that can prove the behavior. Add broader integration or end-to-end coverage only when component boundaries matter. - For a defect, reproduce it before changing the test or implementation when practical. ## Test implementation - Follow nearby fixtures, helpers, naming, and isolation patterns. - Assert public outcomes rather than private implementation details. - Keep tests deterministic. Control time, randomness, network calls, and shared state where needed. - Do not weaken an existing assertion merely to make a failure disappear. ## Evidence - Run the focused test first, then the relevant repository test target and required quality checks. - Separate observed command results from inferred coverage. - Report failed commands with the useful failure context and state what remains unverified. Do not modify production code unless the user also requested a fix or implementation.
Versions
The database has no other skills named doompi-testing.
Database snapshot: 13.11.2026 · package version e3a34f298dd5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90doompi-development
Implement scoped code changes in an existing repository and verify them with its native checks. Use when the user asks to build, change, or fix code, not for a review-only request. - 90doompi-review
Review a code change for concrete defects, regressions, missing tests, and contract violations. Use when the user asks for code review, diff review, or risk assessment, not as a general implementation workflow. - 100testing
This skill should be used when the user asks about "testing", "test coverage", "unit tests", "integration tests", "test organization", "test best practices", "flaky tests", "test isolation", "TDD", "regression tests", or needs guidance on test structure, coverage requirements, and test execution. - 100review-testing
Review test strategy and verification evidence for changed behavior. Use for /review-testing and requests to find test gaps. - 90mcaf-testing
Design or update regression tests for features, defects, and refactors using repository verification commands. Use for meaningful user or system flow coverage and test strategy. - 100loom-test-after-implementation
Implement features first, then write behavior-verification tests against the real public API. Code-first/test-after cycle: implement → refactor → write behavior tests → run tests. Use when: implementing behavior where tests verify outcomes after production code is written.