[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QE9AVBKFC9E8Y29W9TXWA2":3,"skill-same:01M6QE9AVBKFC9E8Y29W9TXWA2":63},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6QE9AVBKFC9E8Y29W9TXWA2","openspec-context-docs",null,"OpenSpec context documentation policy: keep requirements in spec.md and capture narrative context in context\u002Foverview\u002Frationale docs under openspec\u002Fspecs. Use when creating or updating OpenSpec docs, spec context, or onboarding\u002Fguide documentation.","opencue\u002Fgitguardex","opencue","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F271874627?v=4","01M6QDWWMZFB8A08PDTA8D0VJ3","Opencue","01M6QDWWSJGBEGVPMCEJFWVACT",28,"MIT","https:\u002F\u002Fgithub.com\u002Fopencue\u002Fgitguardex\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fopenspec-context-docs\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"docs","context","openspec","openspec context docs","spec","policy","documentation","onboarding","capture","overview","guide","use","requirements","narrative","keep","rationale","2026-11-10 10:12:30",false,"---\nname: openspec-context-docs\ndescription: \"OpenSpec context documentation policy: keep requirements in spec.md and capture narrative context in context\u002Foverview\u002Frationale docs under openspec\u002Fspecs. Use when creating or updating OpenSpec docs, spec context, or onboarding\u002Fguide documentation.\"\n---\n\n# OpenSpec Context Docs\n\n## When to use\n\n- Writing or updating OpenSpec documentation (specs, onboarding, guide, change artifacts).\n- A spec is complete but readers lack background, rationale, examples, or operational notes.\n- You need to preserve rich context without weakening SSOT.\n\n## Core rule: two-layer docs\n\n1) `spec.md` = normative, testable requirements (SHALL\u002FMUST + scenarios).\n2) Context docs = narrative and operational detail that helps humans understand and apply the spec.\n\n## Locations\n\n- Main specs:\n  - `openspec\u002Fspecs\u002F\u003Ccapability>\u002Fspec.md` (requirements)\n  - `openspec\u002Fspecs\u002F\u003Ccapability>\u002Fcontext.md` (preferred)\n- Optional split (if context grows):\n  - `overview.md`, `rationale.md`, `examples.md`, `ops.md` inside the same capability folder.\n- Change-level notes (working context):\n  - `openspec\u002Fchanges\u002F\u003Cchange>\u002Fcontext.md` or `notes.md`\n\n## Detail prompts (add depth without forcing a template)\n\nInclude at least 4 of these in context docs:\n- Purpose \u002F scope \u002F non-goals\n- Decision rationale + alternatives considered\n- Constraints (security, performance, policy)\n- Failure modes \u002F edge cases\n- Example request\u002Fresponse, data shape, or user flow\n- Operational notes (rollout, monitoring, runbooks)\n- Links to related specs\u002Fcontracts\n\n## Sync rule\n\n- After implementation\u002Fverification, promote stable context from change notes into the main context docs.\n- Do not duplicate normative requirements in context docs; link back to `spec.md`.\n- Never create or update a `docs\u002F` directory; keep everything under `openspec\u002F`.\n\n## Prompt snippet\n\n\"Keep `spec.md` strictly for requirements. Add\u002Fupdate `context.md` with purpose, decisions, constraints, failure modes, and at least one concrete example.\"\n","# OpenSpec Context Docs\n\n## When to use\n\n- Writing or updating OpenSpec documentation (specs, onboarding, guide, change artifacts).\n- A spec is complete but readers lack background, rationale, examples, or operational notes.\n- You need to preserve rich context without weakening SSOT.\n\n## Core rule: two-layer docs\n\n1) `spec.md` = normative, testable requirements (SHALL\u002FMUST + scenarios).\n2) Context docs = narrative and operational detail that helps humans understand and apply the spec.\n\n## Locations\n\n- Main specs:\n  - `openspec\u002Fspecs\u002F\u003Ccapability>\u002Fspec.md` (requirements)\n  - `openspec\u002Fspecs\u002F\u003Ccapability>\u002Fcontext.md` (preferred)\n- Optional split (if context grows):\n  - `overview.md`, `rationale.md`, `examples.md`, `ops.md` inside the same capability folder.\n- Change-level notes (working context):\n  - `openspec\u002Fchanges\u002F\u003Cchange>\u002Fcontext.md` or `notes.md`\n\n## Detail prompts (add depth without forcing a template)\n\nInclude at least 4 of these in context docs:\n- Purpose \u002F scope \u002F non-goals\n- Decision rationale + alternatives considered\n- Constraints (security, performance, policy)\n- Failure modes \u002F edge cases\n- Example request\u002Fresponse, data shape, or user flow\n- Operational notes (rollout, monitoring, runbooks)\n- Links to related specs\u002Fcontracts\n\n## Sync rule\n\n- After implementation\u002Fverification, promote stable context from change notes into the main context docs.\n- Do not duplicate normative requirements in context docs; link back to `spec.md`.\n- Never create or update a `docs\u002F` directory; keep everything under `openspec\u002F`.\n\n## Prompt snippet\n\n\"Keep `spec.md` strictly for requirements. Add\u002Fupdate `context.md` with purpose, decisions, constraints, failure modes, and at least one concrete example.\"\n",{"name":5,"description":7},"main","7546eb50cf658dad033c5a047a7ec89c9d1ee7f4",".codex\u002Fskills\u002Fopenspec-context-docs",4,"https:\u002F\u002Fgithub.com\u002Fopencue\u002Fgitguardex","https:\u002F\u002Fgitguardex.com\u002F","https:\u002F\u002Fgithub.com\u002Fopencue","Building in the open. From AI-powered workflows and developer tools to web experiences, automation, and e-commerce — practical software for real-world problems.","2026-11-12 18:11:01",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add opencue\u002Fgitguardex --skill openspec-context-docs",{"tool":55,"command":56},"bunx","bunx skills add opencue\u002Fgitguardex --skill openspec-context-docs",{"tool":58,"command":59},"pnpm","pnpm dlx skills add opencue\u002Fgitguardex --skill openspec-context-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopencue\u002Fgitguardex\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fopenspec-context-docs\u002FSKILL.md",true,[],[64,83,108,133,151,167],{"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":35},"01M6QEBH0VSDT0T2HX5XE3VW5F","opensrc","Fetch exact dependency or external repository source before inspecting internals. Use for package implementation, upstream behavior, or external GitHub source lookup.","https:\u002F\u002Fgithub.com\u002Fopencue\u002Fgitguardex\u002Fblob\u002Fmain\u002Ftemplates\u002Fcodex\u002Fskills\u002Fopensrc\u002FSKILL.md",[],[66,71,72,73,74,75,30,76,77,78,79,80,81,82],"lookup","for","upstream","implementation","dependency","fetch","behavior","Bash","repository","package","github","source",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":94,"publishedAt":35},"01M6QEBDNSWK5R390QHGFWP601","gx-act","Run GitHub Actions workflows locally with nektos\u002Fact before pushing, so CI failures are caught on the laptop and the PR can be squash-merged on the first remote run.","https:\u002F\u002Fgithub.com\u002Fopencue\u002Fgitguardex\u002Fblob\u002Fmain\u002Ftemplates\u002Fcodex\u002Fskills\u002Fgx-act\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[95,96,97,98,81,99,100,101,102,103,104,105,106,107],"gx act","act","pr","workflows","run","actions","first","ci","can","with","remote","squash","github actions",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":117,"publishedAt":35},"01M6QEBAQ8HA4ZGNDS03AB25Y7","guardex-merge-skills-to-dev","Use when you need to merge SKILL.md updates from agent branches\u002Fworktrees into the local base branch (default: dev) with the multiagent-safety flow.","https:\u002F\u002Fgithub.com\u002Fopencue\u002Fgitguardex\u002Fblob\u002Fmain\u002Ftemplates\u002Fcodex\u002Fskills\u002Fguardex-merge-skills-to-dev\u002FSKILL.md",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发",[118,119,120,121,104,122,123,124,125,126,127,128,30,129,130,131,132],"guardex merge skills to dev","guardex","merge","dev","updates","you","local","branches","base","default","worktrees","branch","Safety","flow","multiagent",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":35},"01M6QEB1MG3NCEZ9DP310AAANC","gitguardex","Use for GitGuardex branch\u002Fworktree safety, agent or subagent collision avoidance, file ownership, and gated PR finishing. Not for code-quality review.","https:\u002F\u002Fgithub.com\u002Fopencue\u002Fgitguardex\u002Fblob\u002Fmain\u002Ftemplates\u002Fcodex\u002Fskills\u002Fgitguardex\u002FSKILL.md",[139],{"categoryNo":115,"categoryName":116,"taxonomyType":92,"taxonomyTypeDesc":93},[135,141,72,142,143,144,30,129,145,146,130,147,148,149,97,150],"subagent","ownership","quality review","gated","quality","code-quality","file","worktree","code","review",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":35},"01M6QEAYMVDN8RZCVHQS7YNCBJ","pr-lens","Generate local PR Lens architecture and data-flow diagrams alongside a GitGuardex Codex or Claude PR review.","https:\u002F\u002Fgithub.com\u002Fopencue\u002Fgitguardex\u002Fblob\u002Fmain\u002Fskills\u002Fpr-lens\u002FSKILL.md",[],[97,158,159,160,161,131,162,163,164,165,150,166,135,124],"lens","pr lens","data-flow","data","generate","pr review","architecture","codex","diagrams",{"skillNo":168,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":35},"01M6QEAVDZQRKP05NHQ2AWR3MY","https:\u002F\u002Fgithub.com\u002Fopencue\u002Fgitguardex\u002Fblob\u002Fmain\u002Fskills\u002Fgx-act\u002FSKILL.md",[171],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[96,95,81,104,103,105,106,101,107,102,100,99,97,98]]