Loading...
Loading...
Found 4 Skills
Use before saying an Oracle task is done, fixed, deployed, faster or working - before the final report, before "xong roi", "da sua xong", "deployed", before ending an autopilot session. Collects the evidence from this session - compile errors, INVALID objects against the baseline, lint, journal entries, before/after plans when performance was the point - and reports only what that evidence proves.
Verify a change to this app before calling it done. Use after changing the web, the server, a tool, an agent, a job or a chat (prompt, rules or output contract), when a law of docs/INVARIANTS.md is touched, or when reproducing a bug a person reported. Runs the gate, launches an isolated instance for this checkout, drives it like the person using the app, collects evidence (network, console, trace, accessibility, phone width) and writes the proof/skip report.
Persist, schedule, resume, and hand off monitoring or ownership campaigns that outlive one agent session or disposable workspace. Use when work must be checked repeatedly over days, when creating a new long-term campaign, when transferring ongoing work to a future agent, or when producing a delayed evidence-based report.
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).