[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76S0D3VM8XQQFK8RA6YA7R2":3,"skill-same:01M76S0D3VM8XQQFK8RA6YA7R2":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M76S0D3VM8XQQFK8RA6YA7R2","verify-change",null,"Design and execute a risk-based verification strategy for a software change, bug fix, refactor, migration, configuration update, or release candidate. Use when Codex needs to prove that a change works, choose proportional tests, investigate whether validation is sufficient, or report what remains unverified. Trace claims to evidence across static checks, focused tests, integration boundaries, and runtime behavior instead of merely running the entire test suite.","contextosai\u002Fskills","contextosai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250783517?v=4","01M755ZZB3A7TQ0JMXMQ3V9C6A","Piyush","01M755ZZBYNZNFZBVZ2278BSYT",1,"MIT","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify-change\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: verify-change\ndescription: Design and execute a risk-based verification strategy for a software change, bug fix, refactor, migration, configuration update, or release candidate. Use when Codex needs to prove that a change works, choose proportional tests, investigate whether validation is sufficient, or report what remains unverified. Trace claims to evidence across static checks, focused tests, integration boundaries, and runtime behavior instead of merely running the entire test suite.\n---\n\n# Change Verification\n\nProduce the smallest evidence set that convincingly supports the change's\nclaims and protects its highest-risk invariants.\n\n## Protocol\n\n1. Identify the exact change range and read applicable repository instructions.\n   Preserve unrelated user changes.\n2. Write a claim ledger: each intended behavior, preserved invariant, affected\n   boundary, likely failure mode, and the evidence that could falsify it. Use\n   `references\u002Fverification-matrix.md`.\n3. Classify risk by consequence, reachability, novelty, and reversibility. Raise\n   rigor for authorization, money, destructive writes, migrations, concurrency,\n   public APIs, and silent corruption.\n4. Inspect existing test\u002Fbuild commands and CI configuration. Do not guess a\n   command when the repository declares one.\n5. Order checks for fast information:\n   - syntax\u002Ftype\u002Fstatic validation;\n   - focused tests for changed logic and regression input;\n   - integration tests across affected boundaries;\n   - broader suite\u002Fbuild\u002Fpackage checks;\n   - runtime smoke, migration, compatibility, performance, or security checks\n     only when the risk model calls for them.\n6. Before each expensive check, state which claim it tests. Do not run broad\n   suites merely to create confidence theater.\n7. Interpret results, not exit codes alone. Confirm tests were discovered,\n   assertions exercised the changed path, expected failures did not get\n   swallowed, snapshots\u002Fartifacts are meaningful, and warnings are relevant.\n8. For a bug fix, demonstrate the regression test targets the original failure.\n   Prefer fail-before\u002Fpass-after evidence when safely obtainable without\n   discarding work; otherwise explain the causal link.\n9. For migrations or irreversible operations, verify on disposable data and\n   inspect forward, backward\u002Frollback, partial-failure, and repeated-run paths.\n10. Stop when every material claim has evidence or an explicit gap. Never claim\n    \"fully verified\" from a partial environment.\n\n## Guardrails\n\n- Do not mutate production, publish, deploy, or exercise real side effects\n  without explicit authority.\n- Do not weaken assertions, delete failing tests, or regenerate snapshots solely\n  to obtain green output.\n- Distinguish product failures, test defects, environmental failures, and checks\n  that never ran.\n- Treat flaky success as inconclusive until the nondeterminism is bounded.\n- Report skipped, inaccessible, or environment-dependent checks as gaps with\n  their risk—not as passes.\n\n## Output\n\nLead with the verification verdict: supported, partially supported, or not\nsupported. Summarize evidence by claim, then failures and residual risk. Include\nexact commands and concise results so another engineer can reproduce the proof.\n","# Change Verification\n\nProduce the smallest evidence set that convincingly supports the change's\nclaims and protects its highest-risk invariants.\n\n## Protocol\n\n1. Identify the exact change range and read applicable repository instructions.\n   Preserve unrelated user changes.\n2. Write a claim ledger: each intended behavior, preserved invariant, affected\n   boundary, likely failure mode, and the evidence that could falsify it. Use\n   `references\u002Fverification-matrix.md`.\n3. Classify risk by consequence, reachability, novelty, and reversibility. Raise\n   rigor for authorization, money, destructive writes, migrations, concurrency,\n   public APIs, and silent corruption.\n4. Inspect existing test\u002Fbuild commands and CI configuration. Do not guess a\n   command when the repository declares one.\n5. Order checks for fast information:\n   - syntax\u002Ftype\u002Fstatic validation;\n   - focused tests for changed logic and regression input;\n   - integration tests across affected boundaries;\n   - broader suite\u002Fbuild\u002Fpackage checks;\n   - runtime smoke, migration, compatibility, performance, or security checks\n     only when the risk model calls for them.\n6. Before each expensive check, state which claim it tests. Do not run broad\n   suites merely to create confidence theater.\n7. Interpret results, not exit codes alone. Confirm tests were discovered,\n   assertions exercised the changed path, expected failures did not get\n   swallowed, snapshots\u002Fartifacts are meaningful, and warnings are relevant.\n8. For a bug fix, demonstrate the regression test targets the original failure.\n   Prefer fail-before\u002Fpass-after evidence when safely obtainable without\n   discarding work; otherwise explain the causal link.\n9. For migrations or irreversible operations, verify on disposable data and\n   inspect forward, backward\u002Frollback, partial-failure, and repeated-run paths.\n10. Stop when every material claim has evidence or an explicit gap. Never claim\n    \"fully verified\" from a partial environment.\n\n## Guardrails\n\n- Do not mutate production, publish, deploy, or exercise real side effects\n  without explicit authority.\n- Do not weaken assertions, delete failing tests, or regenerate snapshots solely\n  to obtain green output.\n- Distinguish product failures, test defects, environmental failures, and checks\n  that never ran.\n- Treat flaky success as inconclusive until the nondeterminism is bounded.\n- Report skipped, inaccessible, or environment-dependent checks as gaps with\n  their risk—not as passes.\n\n## Output\n\nLead with the verification verdict: supported, partially supported, or not\nsupported. Summarize evidence by claim, then failures and residual risk. Include\nexact commands and concise results so another engineer can reproduce the proof.\n",{"name":5,"description":7},"main","43b8276ae4a34549906dec6c848cbab4ba32f99a","skills\u002Fverify-change",0,"https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills","https:\u002F\u002Fgithub.com\u002Fcontextosai","Local-first AI memory, agentic workflows, and personal knowledge OS for builders.\r\nOpen-source cognitive layer for notes, tools, context, and automation","2026-10-07 00:08:17",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add contextosai\u002Fskills --skill verify-change",{"tool":38,"command":39},"bunx","bunx skills add contextosai\u002Fskills --skill verify-change",{"tool":41,"command":42},"pnpm","pnpm dlx skills add contextosai\u002Fskills --skill verify-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify-change\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",219,"https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify-change\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fverification-matrix.md",1628,"https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify-change\u002Freferences\u002Fverification-matrix.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M76S0GH6D0VRZ2JFXQF75TY3","template-skill","Replace with a description of what this skill does and when Claude should use it.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Ftemplate\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M76S09DHTPYMC5B5XZMJ8SWG","triage-incident","Triage an active or recent software production incident by establishing impact, stabilizing the system, preserving evidence, building a timestamped timeline, coordinating hypotheses, and choosing reversible mitigations. Use when users report an outage, severe degradation, security or data-integrity event, broken deployment, elevated errors, or ask for incident command, status assessment, mitigation, or investigation support. Prioritize user harm reduction over root-cause completeness and require explicit authority for production mutations.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftriage-incident\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7561WJ328HD8Q6D6R7C6711","review-change","Review a code change for concrete correctness, security, data-integrity, compatibility, concurrency, and operability regressions by reconstructing intent and checking affected invariants and boundary paths. Use for local diffs, commits, branches, patches, or pull requests when the user wants actionable review findings. Report only defects introduced or exposed by the change with precise evidence; do not modify code unless asked to address findings.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Freview-change\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7561S5J5V0FY7ND8FBB2C8Q","repo-orient","Map an unfamiliar software repository from code and configuration. Use when Codex needs to understand a new codebase, locate entry points or ownership boundaries, explain architecture and runtime flow, identify where a change belongs, or prepare for implementation without yet modifying files. Produce an evidence-backed repository map, not a directory listing or README paraphrase.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frepo-orient\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7561M6A7D4T3JE315JAB1BG","refactor-safely","Restructure existing code while preserving externally observable behavior through explicit invariants, characterization evidence, small reversible steps, and continuous verification. Use when the user asks to refactor, simplify, extract, reorganize, modularize, deduplicate, split a component, improve architecture, or pay down technical debt without intentionally changing product behavior. Distinguish refactoring from feature work and stop scope drift from hiding inside structural edits.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frefactor-safely\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7561HX5EKDHE9HV7BMXAAND","readme-polish","Improve a project's README for clarity, structure, and completeness without changing its meaning. Use when the user asks to clean up, polish, or improve a README or project documentation.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Freadme-polish\u002FSKILL.md",[],[]]