Edge case sweep
Skill pipipip169/fable5-handoff/sources/adamentwistle-fable-skills/edge-case-sweep
Enumerate edge cases against a concrete checklist before declaring code complete. Use when implementing or reviewing any function, handler, parser, or data transformation — after the happy path works, before reporting done.From its SKILL.md
npx -y skills add pipipip169/fable5-handoff --skill edge-case-sweepAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 290 tokens by cl100k_base, as published. Nobody here has run it
edge-case-sweep
The happy path is the easy 80%. Sweep this list against every new or changed code path and either handle, explicitly reject, or consciously note each relevant case:
Inputs
- empty:
"",[],{}, zero rows, zero-byte file - absent: null / undefined / missing key / missing flag — distinct from empty
- boundaries: 0, -1, exactly-at-limit, limit+1, first and last element
- huge: 10^6 items, multi-GB file, pathologically long string
- weird text: unicode, emoji, RTL, newlines-in-fields, quotes, leading/trailing whitespace, case variants
- duplicates and unsorted order where uniqueness/order is assumed
State & time
- called twice (idempotency), called concurrently, retried after partial success
- stale state: file changed since read, record deleted between fetch and update
- timezone, DST, end-of-month/year, clock skew
Environment
- dependency down / slow / returning errors: what does the caller see?
- permissions denied, disk full, network cut mid-operation
For each case that applies: decide handle vs reject-loudly. The unacceptable outcome is silent wrong behavior. If a case is deliberately unhandled, say so in the completion report — a stated limitation is fine, a hidden one is a bug report waiting.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.