experience-checklist

Applies checklist-based testing and error guessing to externalize testing experience into enumerated test cases.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hakkadaikon/hymme --skill experience-checklist-hakkadaikon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experience-checklist
Source: https://github.com/Hakkadaikon/hymme/tree/main/skills/experience-checklist
Command: npx skills add https://github.com/Hakkadaikon/hymme --skill experience-checklist-hakkadaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Experience-based testing techniques like error guessing are informal and person-dependent, making coverage unverifiable and knowledge non-transferable. This Skill turns tester intuition and past defect history into numbered checklists (CL-ID / EG-ID) with explicit oracles, so every item is traceable to a test case and nothing is silently skipped. ## Core Features & Use Cases - Checklist-Based Testing: Aggregates domain standards (WCAG, OWASP), internal rules, and past defects into sourced checklist items, then splits them into machine-verifiable items (converted to tests) and human-judgment items (kept in documents). - Error Guessing: Collects failure patterns from three sources (past bugs, generic hostile inputs like empty/null/huge values/special characters/concurrency, and target-specific weak spots), assigns each an oracle, and maps them one-to-one into it.each test cases. - Reverse-Traceability Audits: Verifies completeness by grep-matching every EG-ID/CL-ID in the checklist against test descriptions, and promotes found defects into equivalence partitioning, boundary value, and regression assets. - Use Case: Before releasing a string utility like slugify, enumerate nasty inputs (empty, whitespace-only, 10k characters, non-ASCII, path traversal) as EG-01 through EG-05, then generate one Vitest case per item and confirm the ID counts match. ## Quick Start Ask the AI to apply the experience-checklist skill to build an error-guessing checklist with EG-IDs and matching Vitest cases for your target function.

Frequently Asked Questions about experience-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I do error guessing in software testing systematically?

Error guessing becomes systematic by collecting failure patterns from three sources: past bugs, generic hostile inputs (empty, null, zero, huge values, special characters, concurrency), and target-specific weak spots. Number each item (EG-01, EG-02...), assign an oracle, and write one test case per item.

What is checklist-based testing and when should I use it?

Checklist-based testing derives test items from experience, domain knowledge, and regulations, then checks off every item. Use it for recurring known requirements like accessibility checklists, release checklists, or industry regulations, as an index that prevents forgetting techniques rather than a replacement for them.

How do I verify my error guessing checklist has full test coverage?

Verify coverage by reverse-matching IDs: run grep -o 'EG-[0-9]*' on the test file, sort unique, and compare the count against checklist items. Any mismatch reveals items without test cases. Also confirm all three collection sources contributed at least one item.

What is the difference between error guessing and checklist-based testing?

Error guessing targets inputs likely to break the system based on intuition and past defects, while checklist-based testing enumerates conditions that must be satisfied. One starts from breaking, the other from fulfilling; both externalize experience into lists that get fully consumed.

When should I not rely on error guessing alone for test design?

Error guessing cannot claim input-space coverage because it is experience-driven and non-formal. Use it only as a finishing complement to systematic techniques like equivalence partitioning and boundary value analysis, and promote found defects back into those systematic assets.