[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73FZPWA65SZCF06J5Q3EN7H":3,"skill-same:01M73FZPWA65SZCF06J5Q3EN7H":129},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M73FZPWA65SZCF06J5Q3EN7H","release-readiness-reviewer",null,"Assess release readiness, rollback, migrations, feature flags, monitoring, documentation, and breaking changes.","domehahn\u002Fskcr","domehahn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F41511445?v=4","01M735R3R9KEBEJ6D5YYAE9A61","Dominik Hahn","01M735R3SCNX1SGB3T840Z1H3H",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"release-readiness-reviewer\"\ndescription: \"Assess release readiness, rollback, migrations, feature flags, monitoring, documentation, and breaking changes.\"\nversion: \"1.0.0\"\nsince: \"2026-09-09\"\nlast_modified: \"2026-09-09\"\nauthors:\n  - \"platform-engineering\"\nstability: \"stable\"\nmin_platform_version:\n  codex: \"unknown\"\n  amazon-q: \"unknown\"\n  antigravity: \"unknown\"\n  auggie: \"unknown\"\n  bob: \"unknown\"\n  claude-code: \"unknown\"\n  cline: \"unknown\"\n  codebuddy: \"unknown\"\n  continue: \"unknown\"\n  costrict: \"unknown\"\n  crush: \"unknown\"\n  github-copilot: \"unknown\"\n  gitlab-duo: \"unknown\"\n  factory: \"unknown\"\n  forgecode: \"unknown\"\n  opencode: \"unknown\"\n  openhands: \"unknown\"\n  cursor: \"unknown\"\n  roo-code: \"unknown\"\n  kiro: \"unknown\"\n  junie: \"unknown\"\n  gemini-cli: \"unknown\"\n  iflow: \"unknown\"\n  kilocode: \"unknown\"\n  kimi: \"unknown\"\n  lingma: \"unknown\"\n  pi: \"unknown\"\n  qoder: \"unknown\"\n  qwen: \"unknown\"\n  windsurf: \"unknown\"\n  ollama: \"unknown\"\ndeprecated_since:\nreplaces:\nsupersedes: []\nchangelog:\n  - version: \"1.0.0\"\n    date: \"2026-09-09\"\n    change: \"Initial generated production-ready SDLC \u002F DevSecOps skill\"\n---\n# Release Readiness Reviewer\n\n## Purpose\n\nDetermine whether a change or system is ready for release by reviewing test status, security findings, known issues, rollback, migrations, monitoring, alerts, runbooks, feature flags, approvals, release notes, support readiness, and go\u002Fno-go recommendation.\n\n## Goal and behavioral contract\n\nThe authoritative Goal and artifact references are defined in `descriptor.yaml`. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in `contract.yaml`. MCP\u002FA2A trust boundaries and the reviewed execution closure live in `integrations\u002F` and `dependencies.yaml`; ASPS and assurance requirements live in `assurance.yaml`.\n\nTreat those declarations as mandatory execution constraints. `skcr` validates requirements but does not claim verification or enforce them at runtime.\n\n## When to use\n\n- A release, deployment, version bump, migration, or production rollout needs go\u002Fno-go review.\n- Known issues, security findings, rollback, monitoring, or support readiness are unclear.\n- Feature flags, staged rollout, or compatibility risk must be assessed.\n- Release notes, approvals, or operational ownership need validation.\n- The central agent routes to release readiness review.\n\n## Operating model\n\n1. Collect release scope, changed artifacts, validation status, deployment plan, and owners.\n2. Evaluate blockers across tests, security, migrations, rollback, monitoring, docs, support, and approvals.\n3. Separate go\u002Fno-go criteria from follow-up work and known accepted risks.\n4. Assess rollout strategy, feature flags, blast radius, and recovery time.\n5. Return go, conditional go, or no-go with explicit blockers.\n\n## Spec-Driven Change Context\n\n- Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.\n- For non-trivial changes, prefer a checked-in change artifact or equivalent proposal\u002Fdesign\u002Ftasks record before implementation begins.\n- Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.\n- Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.\n- During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.\n- After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.\n- If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal\u002Fspec\u002Ftasks outline instead of relying on chat-only intent.\n\n## Skill-Specific Review Scope\n\n- Test status, validation evidence, security findings, and known issues.\n- Rollback, migrations, compatibility, feature flags, and staged rollout.\n- Monitoring, alerts, runbooks, support readiness, and ownership.\n- Approvals, release notes, communication, and go\u002Fno-go decision.\n- Blockers, exceptions, residual risk, and follow-up actions.\n\n## Skill-Specific Checklist\n\n- [ ] Verify required tests, builds, scans, migrations, and smoke checks are complete.\n- [ ] Identify unresolved blockers and classify known issues by user impact.\n- [ ] Check open security findings, exceptions, owners, and expiry.\n- [ ] Verify rollback plan, rollback trigger, rollback owner, and data rollback constraints.\n- [ ] Check migration forward\u002Fbackward compatibility, idempotency, and backup plan.\n- [ ] Verify monitoring dashboards, alerts, SLO indicators, and post-deploy validation.\n- [ ] Check runbooks, escalation contacts, on-call coverage, and support readiness.\n- [ ] Check release notes, changelog, customer communication, and breaking-change guidance.\n- [ ] Identify feature flag, canary, staged rollout, kill switch, or traffic-shaping options.\n- [ ] Confirm approvals, release owner, deployment window, and freeze constraints.\n- [ ] Check dependencies on external services, infra capacity, and version compatibility.\n- [ ] Produce go\u002Fno-go with explicit conditions.\n\n## Decision Rules\n\n- If rollback is impossible or untested for high-impact change, no-go unless risk is accepted by owner.\n- If Critical\u002FHigh security findings are open without approved exception, no-go.\n- If migrations can corrupt or lose data without backup and validation, no-go.\n- If monitoring cannot detect release failure, require conditional go or no-go by impact.\n- If known issues affect core user journeys, require mitigation, communication, or staged rollout.\n- If release notes omit breaking changes or migrations, block external release readiness.\n\n## Finding Categories\n\n- Missing go\u002Fno-go evidence or owner.\n- Failed, skipped, stale, or insufficient validation gate.\n- Open security, compliance, privacy, or known-issue blocker.\n- Rollback, migration, compatibility, or data-safety gap.\n- Monitoring, alerting, runbook, on-call, or support readiness gap.\n- Release notes, communication, approval, or change-management gap.\n\n## Severity Guidance\n\n- Critical: immediate exploitability or operational failure can expose secrets, regulated data, production safety, or release integrity.\n- High: credible security, reliability, compliance, rollback, or user-impact risk requires owner action before merge or release.\n- Medium: meaningful maintainability, validation, documentation, or process gap should be tracked and resolved.\n- Low: advisory improvement, clarity issue, or hardening opportunity with limited immediate impact.\n\n## DevSecOps Guardrails\n\n- Do not read secrets, `.env` files, private keys, production credentials, masked CI\u002FCD variables, database dumps, or sensitive logs unless explicitly required.\n- Do not push, deploy, publish, merge, or create releases unless explicitly asked.\n- Prefer merge requests, reviewable diffs, and auditable validation evidence.\n- Prefer least privilege, minimal changes, and explicit rollback notes.\n- Do not fabricate test results, repository state, commands, security findings, or validation outcomes.\n- Report assumptions, uncertainty, residual risk, and validation gaps clearly.\n\n## Output Requirements\n\n- Go\u002Fno-go summary with blockers, conditions, and owner.\n- Release checklist covering tests, security, migrations, rollback, monitoring, docs, support, and approvals.\n- Known issues table with severity, impact, mitigation, and acceptance owner.\n- Rollback and post-deploy validation plan.\n- Feature flag, canary, staged rollout, or kill-switch recommendation.\n- Residual risks and follow-up actions with deadlines.\n\n## Acceptance Criteria\n\n- All release blockers are resolved or explicitly accepted.\n- Rollback, migration, monitoring, and support readiness are verified.\n- Security findings and known issues have owner-approved disposition.\n- Release notes cover breaking changes, migrations, and operational impact.\n- Go\u002Fno-go recommendation follows evidence.\n- Post-release validation and escalation path are defined.\n\n## Anti-Patterns\n\n- Treating green CI as complete release readiness.\n- Approving release with no rollback trigger or owner.\n- Ignoring known issues because they are documented elsewhere.\n- Skipping monitoring and support readiness until after deployment.\n- Accepting security findings without expiry and owner.\n- Publishing breaking changes without migration guidance.\n\n## Changelog\n\n### 1.0.0 - 2026-09-09\n\n- Initial generated production-ready SDLC \u002F DevSecOps skill.\n","# Release Readiness Reviewer\n\n## Purpose\n\nDetermine whether a change or system is ready for release by reviewing test status, security findings, known issues, rollback, migrations, monitoring, alerts, runbooks, feature flags, approvals, release notes, support readiness, and go\u002Fno-go recommendation.\n\n## Goal and behavioral contract\n\nThe authoritative Goal and artifact references are defined in `descriptor.yaml`. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in `contract.yaml`. MCP\u002FA2A trust boundaries and the reviewed execution closure live in `integrations\u002F` and `dependencies.yaml`; ASPS and assurance requirements live in `assurance.yaml`.\n\nTreat those declarations as mandatory execution constraints. `skcr` validates requirements but does not claim verification or enforce them at runtime.\n\n## When to use\n\n- A release, deployment, version bump, migration, or production rollout needs go\u002Fno-go review.\n- Known issues, security findings, rollback, monitoring, or support readiness are unclear.\n- Feature flags, staged rollout, or compatibility risk must be assessed.\n- Release notes, approvals, or operational ownership need validation.\n- The central agent routes to release readiness review.\n\n## Operating model\n\n1. Collect release scope, changed artifacts, validation status, deployment plan, and owners.\n2. Evaluate blockers across tests, security, migrations, rollback, monitoring, docs, support, and approvals.\n3. Separate go\u002Fno-go criteria from follow-up work and known accepted risks.\n4. Assess rollout strategy, feature flags, blast radius, and recovery time.\n5. Return go, conditional go, or no-go with explicit blockers.\n\n## Spec-Driven Change Context\n\n- Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.\n- For non-trivial changes, prefer a checked-in change artifact or equivalent proposal\u002Fdesign\u002Ftasks record before implementation begins.\n- Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.\n- Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.\n- During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.\n- After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.\n- If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal\u002Fspec\u002Ftasks outline instead of relying on chat-only intent.\n\n## Skill-Specific Review Scope\n\n- Test status, validation evidence, security findings, and known issues.\n- Rollback, migrations, compatibility, feature flags, and staged rollout.\n- Monitoring, alerts, runbooks, support readiness, and ownership.\n- Approvals, release notes, communication, and go\u002Fno-go decision.\n- Blockers, exceptions, residual risk, and follow-up actions.\n\n## Skill-Specific Checklist\n\n- [ ] Verify required tests, builds, scans, migrations, and smoke checks are complete.\n- [ ] Identify unresolved blockers and classify known issues by user impact.\n- [ ] Check open security findings, exceptions, owners, and expiry.\n- [ ] Verify rollback plan, rollback trigger, rollback owner, and data rollback constraints.\n- [ ] Check migration forward\u002Fbackward compatibility, idempotency, and backup plan.\n- [ ] Verify monitoring dashboards, alerts, SLO indicators, and post-deploy validation.\n- [ ] Check runbooks, escalation contacts, on-call coverage, and support readiness.\n- [ ] Check release notes, changelog, customer communication, and breaking-change guidance.\n- [ ] Identify feature flag, canary, staged rollout, kill switch, or traffic-shaping options.\n- [ ] Confirm approvals, release owner, deployment window, and freeze constraints.\n- [ ] Check dependencies on external services, infra capacity, and version compatibility.\n- [ ] Produce go\u002Fno-go with explicit conditions.\n\n## Decision Rules\n\n- If rollback is impossible or untested for high-impact change, no-go unless risk is accepted by owner.\n- If Critical\u002FHigh security findings are open without approved exception, no-go.\n- If migrations can corrupt or lose data without backup and validation, no-go.\n- If monitoring cannot detect release failure, require conditional go or no-go by impact.\n- If known issues affect core user journeys, require mitigation, communication, or staged rollout.\n- If release notes omit breaking changes or migrations, block external release readiness.\n\n## Finding Categories\n\n- Missing go\u002Fno-go evidence or owner.\n- Failed, skipped, stale, or insufficient validation gate.\n- Open security, compliance, privacy, or known-issue blocker.\n- Rollback, migration, compatibility, or data-safety gap.\n- Monitoring, alerting, runbook, on-call, or support readiness gap.\n- Release notes, communication, approval, or change-management gap.\n\n## Severity Guidance\n\n- Critical: immediate exploitability or operational failure can expose secrets, regulated data, production safety, or release integrity.\n- High: credible security, reliability, compliance, rollback, or user-impact risk requires owner action before merge or release.\n- Medium: meaningful maintainability, validation, documentation, or process gap should be tracked and resolved.\n- Low: advisory improvement, clarity issue, or hardening opportunity with limited immediate impact.\n\n## DevSecOps Guardrails\n\n- Do not read secrets, `.env` files, private keys, production credentials, masked CI\u002FCD variables, database dumps, or sensitive logs unless explicitly required.\n- Do not push, deploy, publish, merge, or create releases unless explicitly asked.\n- Prefer merge requests, reviewable diffs, and auditable validation evidence.\n- Prefer least privilege, minimal changes, and explicit rollback notes.\n- Do not fabricate test results, repository state, commands, security findings, or validation outcomes.\n- Report assumptions, uncertainty, residual risk, and validation gaps clearly.\n\n## Output Requirements\n\n- Go\u002Fno-go summary with blockers, conditions, and owner.\n- Release checklist covering tests, security, migrations, rollback, monitoring, docs, support, and approvals.\n- Known issues table with severity, impact, mitigation, and acceptance owner.\n- Rollback and post-deploy validation plan.\n- Feature flag, canary, staged rollout, or kill-switch recommendation.\n- Residual risks and follow-up actions with deadlines.\n\n## Acceptance Criteria\n\n- All release blockers are resolved or explicitly accepted.\n- Rollback, migration, monitoring, and support readiness are verified.\n- Security findings and known issues have owner-approved disposition.\n- Release notes cover breaking changes, migrations, and operational impact.\n- Go\u002Fno-go recommendation follows evidence.\n- Post-release validation and escalation path are defined.\n\n## Anti-Patterns\n\n- Treating green CI as complete release readiness.\n- Approving release with no rollback trigger or owner.\n- Ignoring known issues because they are documented elsewhere.\n- Skipping monitoring and support readiness until after deployment.\n- Accepting security findings without expiry and owner.\n- Publishing breaking changes without migration guidance.\n\n## Changelog\n\n### 1.0.0 - 2026-09-09\n\n- Initial generated production-ready SDLC \u002F DevSecOps skill.\n",{"name":5,"since":25,"authors":26,"version":28,"replaces":6,"changelog":29,"stability":32,"supersedes":33,"description":7,"last_modified":25,"deprecated_since":6,"min_platform_version":34},"2026-09-09",[27],"platform-engineering","1.0.0",[30],{"date":25,"change":31,"version":28},"Initial generated production-ready SDLC \u002F DevSecOps skill","stable",[],{"pi":35,"bob":35,"kimi":35,"kiro":35,"qwen":35,"cline":35,"codex":35,"crush":35,"iflow":35,"junie":35,"qoder":35,"auggie":35,"cursor":35,"lingma":35,"ollama":35,"factory":35,"amazon-q":35,"continue":35,"costrict":35,"kilocode":35,"opencode":35,"roo-code":35,"windsurf":35,"codebuddy":35,"forgecode":35,"openhands":35,"gemini-cli":35,"gitlab-duo":35,"antigravity":35,"claude-code":35,"github-copilot":35},"unknown","main","850948b1e2e668b3ddfc2ac2959286d4190a8a4a",".agents\u002Fskills\u002Frelease-readiness-reviewer","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr","https:\u002F\u002Fgithub.com\u002Fdomehahn","Proud to live. Love to code and explore. DevSecOps | Cloud & Cloud Native | Java | Go | Python | IaC | AI ","2026-09-11 04:40:53",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add domehahn\u002Fskcr --skill release-readiness-reviewer",{"tool":49,"command":50},"bunx","bunx skills add domehahn\u002Fskcr --skill release-readiness-reviewer",{"tool":52,"command":53},"pnpm","pnpm dlx skills add domehahn\u002Fskcr --skill release-readiness-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002FSKILL.md",true,[57,63,69,73,77,81,85,89,93,97,101,105,109,113,119,123],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002FREADME.md","ASSET","资产文件",147,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Fassets\u002FREADME.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"assurance.yaml","REFERENCE","参考文档",393,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Fassurance.yaml",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"CHANGELOG.md",133,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002FCHANGELOG.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"contract.yaml",3776,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Fcontract.yaml",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"dependencies.yaml",85,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Fdependencies.yaml",{"path":82,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":83,"sourceHtmlUrl":84},"descriptor.yaml",671,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Fdescriptor.yaml",{"path":86,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":87,"sourceHtmlUrl":88},"evals\u002Fbaseline.yaml",2227,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Fevals\u002Fbaseline.yaml",{"path":90,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":91,"sourceHtmlUrl":92},"evals\u002FREADME.md",732,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Fevals\u002FREADME.md",{"path":94,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":95,"sourceHtmlUrl":96},"integrations\u002Fa2a.yaml",292,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Fintegrations\u002Fa2a.yaml",{"path":98,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":99,"sourceHtmlUrl":100},"integrations\u002Fmcp.yaml",32,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Fintegrations\u002Fmcp.yaml",{"path":102,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":16},"LICENSE","许可证",214,{"path":106,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":107,"sourceHtmlUrl":108},"README.md",1344,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002FREADME.md",{"path":110,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002FREADME.md",180,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Freferences\u002FREADME.md",{"path":114,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002FREADME.md","SCRIPT","脚本",215,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Fscripts\u002FREADME.md",{"path":120,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":121,"sourceHtmlUrl":122},"tests\u002FREADME.md",179,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002Ftests\u002FREADME.md",{"path":124,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":127,"sourceHtmlUrl":128},"VERSION","OTHER","其他",6,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-readiness-reviewer\u002FVERSION",[130,138,146,154,162,170],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M7419KQMCNS14XW21KVG78J3","vulnerability-management-coordinator","Assess CVE triage, prioritization, SLAs, exploitability, asset criticality, exceptions, risk acceptance, and remediation tracking.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fvulnerability-management-coordinator\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fvulnerability-management-coordinator\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M7419GW8E90CEERTQTZ3MTYR","verification-reviewer","Review diffs, validate acceptance criteria, inspect test results, and find missed requirements.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fverification-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fverification-reviewer\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":20},"01M7419CTW726KC0YN9F2E739T","universal-skill-creator","Create, adapt, validate, and optimize reusable agent skills across agentic platforms.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Funiversal-skill-creator\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Funiversal-skill-creator\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":20},"01M74199GKQYVD5KER7CZ8F2D6","threat-modeler","Identify assets, trust boundaries, abuse cases, attack paths, threats, and required security controls.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fthreat-modeler\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fthreat-modeler\u002FSKILL.md",[],[],{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":20},"01M74196JRAY93SRVX6X6CDMDF","test-strategy-engineer","Design and generate unit, integration, regression, security, and end-to-end test strategies.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Ftest-strategy-engineer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Ftest-strategy-engineer\u002FSKILL.md",[],[],{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":174,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":20},"01M74193K4YBY6JHZSVQ92NS9X","sre-reliability-reviewer","Assess SLOs, SLIs, error budgets, capacity, degradation, timeouts, retries, circuit breakers, load shedding, and operational risks.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fsre-reliability-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fsre-reliability-reviewer\u002FSKILL.md",[],[]]