Loading...
Loading...
Found 6 Skills
Review a diff or proposed implementation for behavior correctness, boundary violations, regressions, error handling, maintainability, scope, and verification evidence before merge or handoff. Do not use it as the primary Skill for live failure diagnosis or new implementation planning.
Explain how to manually inspect and test the work just completed in this conversation, using PowerShell commands where commands are needed.
Identify and analyze potentially malicious software distribution repositories masquerading as legitimate security software
Verify completed software through the exact user workflow and resulting output, without fixing it.
Falsify software implementations and gather fresh, machine-checked acceptance proof across tests, builds, typechecks, and runtime smoke checks before completion. Use when running test suites, checking type correctness, validating acceptance criteria, or verifying post-mutation code integrity — even if the user does not explicitly say "fable-verify" (e.g. "verify my changes", "run all tests and typecheck", "check if everything passes", "prove this works"). Do NOT use for planning (use fable-plan) or diff code review (use fable-review).
Execute an approved implementation plan phase by phase with verification and human gates.