用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/PiLastDigit/TRIP-workflow --skill trip-test命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | TRIP-test |
| description | Write/run tests following project standards (deep test authoring) |
| disable-model-invocation | true |
| argument-hint | component or feature to test |
You are now in testing mode for [PROJECT_NAME].
This skill is the deep test-authoring reference: the TRIP-2-implement testing gate points here for heavy authoring work and full guidance. Invoke it standalone for test backfill or coverage work outside an implementation session.
Before testing, you MUST read:
Test: $ARGUMENTS
# [ADAPT_TO_PROJECT: Replace with actual test commands during Init]
# Run all tests
[TEST_COMMAND_ALL]
# Run specific test
[TEST_COMMAND_SPECIFIC]
# With coverage
[TEST_COMMAND_COVERAGE]
[ADAPT_TO_PROJECT: Describe where tests are located and naming conventions during Init]
Unit Tests:
Integration Tests:
What to Test:
Seam ladder, cheapest first: exported pure helper → injectable client/adapter → module mock → integration/emulator test. Take the first rung that works; refactor for a seam only if the refactor is smaller than the feature you're shipping — otherwise it's coverage debt. Before refactoring legacy code, pin it with characterization tests (assert current behavior as-is, then refactor safely).
Uncovered risky paths: one line each in docs/4-unit-tests/COVERAGE-DEBT.md (path | why hard | escape plan). Delete a ledger line in the same change that gives its path meaningful coverage.
After completing tests, create a summary file:
File: docs/4-unit-tests/wa_vx.y.z_test.md
(a = project week, x.y.z = version)
Content:
# Test Summary - Week a, V. x.y.z
## What Was Tested
[List of tested components/functions]
## Test Results
- Total tests: X
- Passed: X
- Failed: X
- Coverage: X%
## Key Findings
[Any issues discovered, edge cases found, etc.]
## Notes
[Additional context or recommendations]