Update to Riqor

{
  "description": "Use for non-trivial coding, debugging, migration, review, or end-to-end implementation where Codex must inspect the real flow, make a bounded change, and provide fresh verification evidence before completion",
  "included_files": [],
  "name": "evidence-engineering",
  "skill_md_contents": "---\nname: evidence-engineering\ndescription: Use for non-trivial coding, debugging, migration, review, or end-to-end implementation where Codex must inspect the real flow, make a bounded change, and provide fresh verification evidence before completion\n---\n\n# Evidence Engineering\n\n1. Convert the request and active repository rules into observable acceptance criteria\n2. Inspect the repository, package manager, dirty state, relevant callers, tests, and existing patterns before editing\n3. Select only the skills and tools that directly match the task\n4. Prefer deletion or reuse, then platform features, then installed dependencies, then the minimum new code\n5. For unknown failures, trace the root cause before proposing a fix\n6. For behavior changes, write or identify a check that fails before the change and passes after it\n7. Preserve unrelated user changes and keep credentials out of prompts, logs, artifacts, and commits\n8. Run the smallest focused check that would catch the defect, then required project gates\n9. Use an independent reviewer for high-risk security, data, release, or cross-project changes\n10. Finish with changed files, checks and exact outcomes, and anything not verified\n\nDo not claim completion from a plan, a diff, an earlier agent report, or confidence alone\n"
}