fix-research-unknowns
Research unfamiliar libraries, APIs, platforms, or versions before changing code that depends on them, using version-specific primary docs, changelogs, and upstream issues, and confirm with a small probe. Use whenever a fix relies on third-party behavior you have not verified.
71
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Research Before Changing
Procedure
- Find the exact installed version (lockfile,
/version, API version header). - Read primary sources for that version: vendor docs, changelog, migration notes. Check semantics that fixes often get wrong: error codes, retries, idempotency keys, webhook signatures, time zones, caching.
- Search upstream issues for your exact symptom and deployment shape; an upstream bug may need a workaround plus a pinned version.
- Probe: a tiny script that confirms the documented behavior in this environment before you build on it.
- Record each finding: source URL, version, claim, probe result.
Exit criteria
Every third-party assumption in the fix plan has a source and a probe result.
Counterpart of tester skill: qa-research-unknowns.
- Repository
itsablabla/qa-bug-agent-skills
- Revision
9a6f628
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.