test-extract
Skill0 starsChanged 17 days agoNo licenceView on GitHub
test-design の 0 段(振る舞い抽出)。対象(機能、モジュール、API、PR 差分)から「テストすべき振る舞い」を T-ID 採番チェックリスト台帳(tasks/test-design/<対象名>.md)へ網羅的に出し切る。 「テストすべき振る舞いを洗い出して」「テスト観点を出して」「T-ID 台帳」と言われたとき、 または test-design ルーターから 0 段として委譲されたときに使用する。既存テストのレビューでも 最初にこの台帳を作る(台帳を両向きに読んで抜け・根拠なしテストを見つける)。 後続の test-catalog(手法選定)はこの台帳が完成(全 T-ID `[x]`・欠番なし)してからでないと進めない。 通常は test-design ルーター経由で使う。
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mrieck/snipkiwi-design-extracttheir own version, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mrieck/snipkiwi-design-extract★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- ai-nondeterministicSkill
- blackbox-cause-effectSkill
- blackbox-coveringSkill
- blackbox-partitionSkill
- blackbox-stateSkill
- commit-flowSkill
- diff-reviewSkill
- experience-checklistSkill
- experience-exploratorySkill
- experience-scenarioSkill
- flakiness-concurrencySkill
- flakiness-externalSkill
- flakiness-valueSkill
- formal-verificationSkill
- generative-fuzzingSkill
- generative-propertySkill
- gh-ci-investigateSkill
- good-test-principlesSkill
- ledger-flowSkill
- levels-operationalSkill
- levels-serviceSkill
- levelsSkill
- levels-systemSkill
- loopeng-extractSkill
- loopeng-formalizeSkill
- loopeng-gherkinSkill
- loop-engineeringSkill
- loopeng-modelcheckSkill
- loopeng-smtSkill
- loopeng-tracecheckSkill
- micro-commitSkill
- mutation-testingSkill
- nonfunctional-attributesSkill
- nonfunctional-perfSkill
- nonfunctional-resilienceSkill
- oracle-differentialSkill
- oracle-model-basedSkill
- oracle-past-outputSkill
- oracle-relationalSkill
- pr-createSkill
- process-staticSkill
- rebase-flowSkill
- reset-flowSkill
- review-feedbackSkill
- strategy-allocationSkill
- strategy-operationsSkill
- tdd-cycleSkill
- tdd-green-strategySkill
- test-catalogSkill
- test-design-qualitySkill
- test-designSkill
- test-doublesSkill
- testing-principlesSkill
- test-structure-anatomySkill
- test-structure-lifecycleSkill
- test-target-designSkill
- test-targetedSkill
- test-verifySkill
- using-hymmeSkill
- verifiabilitySkill
- The first 60 shown.
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.