Diagnose and fix defects using Veris twins to test changed application behavior.
npx skills add https://github.com/veris-ai/plugins --skill fix-veris-ai
Please help me install this Agent Skill. Skill: fix Source: https://github.com/veris-ai/plugins/tree/main/veris/skills/fix Command: npx skills add https://github.com/veris-ai/plugins --skill fix-veris-ai
gh issue view) or prompt, inspects affected code, and reproduces failures through the application or twin fault injection. - Twin-Backed Verification: Runs the repository's existing integration tests against the sandbox twin, asserting responses and confirming traffic via receipts and traces. - Evidence and Handoff: Summarizes changes with cited evidence, updates .veris/NOTES.md findings, and follows the repository's PR conventions. - Use Case: Given an issue like "create_invoice duplicates the invoice when the response is lost", reproduce the retry behavior against the twin, fix the idempotency handling, and verify the affected caller passes with current-run twin evidence. ## Quick Start Ask the assistant to fix a defect by providing an issue link or prompt, for example: run the fix command for https://github.com/org/repo/issues/42 and verify the changed behavior against the Veris twin.High-intent search queries and answers about installing and using this skill.
Provide an issue link or prompt describing the defect. The Skill reads the issue, inspects the affected code, reproduces the failure through the application or twin fault injection, implements the fix, and runs the affected test against the Veris twin.
Run the repository's existing integration test through the Veris sandbox, which reroutes outbound HTTP(S) to a twin of the vendor service. The test asserts the expected outcome and the run's receipt shows the application traffic reached the twin.
CLI-owned workflows need the veris CLI signed in and the repository wired by setup. Plugin-managed sessions use the OpenCode plugin's remote tools instead, so local CLI installation and Docker are not prerequisites for that path.
Rerun setup only when a handoff step is missing, the connection is broken, or the change invalidates its wiring, such as adding a vendor service or hostname. An application assertion failure alone is not a reason to redo setup.
For changes with no meaningful vendor interaction, skip Veris setup and twin work entirely. Use the repository's own validation and state that scope in the result.
yoanbernabeuConfigures Qdrant as GrepAI's vector storage backend for large codebases.
DayMoonDevelopmentCreate a pull request for a monorepo sibling and link it to a Linear issue.
ArthTech-AIFetch current Railway documentation to answer platform questions accurately.
DazlarusGuides mocking, stubbing, fakes, and test isolation strategies for Python unit tests.