[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AB71CFH8ZKF0QPV5H9QPS0":3,"skill-same:01M7AB71CFH8ZKF0QPV5H9QPS0":47},{"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":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7AB71CFH8ZKF0QPV5H9QPS0","security-maintenance",null,"framework\u002Fruntime\u002Fdependencyの脆弱性情報を収集し、projectへの実影響と優先度を判定してticket\u002Freleaseへ反映する時に使用する。","rebuildup\u002Fproject-init","rebuildup","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F176191237?v=4","01M7AB3QGQ73Q2YNFNFGPAVVRX","samuido","01M7AB3QHEEN3RPZSTXYW3062Y",2,"MIT","https:\u002F\u002Fgithub.com\u002Frebuildup\u002Fproject-init\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-maintenance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: security-maintenance\ndescription: framework\u002Fruntime\u002Fdependencyの脆弱性情報を収集し、projectへの実影響と優先度を判定してticket\u002Freleaseへ反映する時に使用する。\n---\n\n# Security Maintenance\n\nsecurity updateは単純なCVSS順ではなく、projectへの実到達可能性とrelease riskまで含めて優先順位を付ける。\n\n未知のsource vulnerability探索は `security-audit` が所有する。そこで `confirmed` になったfindingは本Skillへhandoffし、advisoryと同じproject-aware priority \u002F remediation \u002F release workflowへ統合する。`needs_validation` をconfirmed vulnerabilityとしてpriority化しない。\n\n## 1. Source priority\n\n初期化時および継続maintenance時に、実際に使用しているversionを基準に次を確認する。\n\n1. framework\u002Fruntime\u002FSDK official security advisories\n2. official release notes \u002F security announcements\n3. language\u002Fpackage ecosystem official advisory source\n4. GitHub Security Advisories \u002F dependency alerts\n5. maintainer issue \u002F patch release information\n6. trusted secondary source\n\n一般ニュースやSNSだけをsecurity SoTにしない。\n\n## 2. Inventory\n\n最低限把握する:\n\n- direct dependencies\n- security-sensitive transitive dependencies\n- framework\u002Fruntime\u002FSDK versions\n- container\u002Fbase image\n- OS\u002Fruntime packages when relevant\n- build\u002Fdeploy toolchain\n- externally exposed services\u002Fendpoints\n- auth\u002Fsession\u002Fcrypto\u002Fstorage\u002Fnetwork boundaries\n\nlockfileやgenerated SBOM等、再現可能なinventoryを優先する。\n\n## 3. Prioritization\n\nseverityだけで決めない。最低限次を評価する。\n\n- advisory severity \u002F CVSS等\n- exploitability \u002F exploit maturity\n- projectでvulnerable pathがreachableか\n- internet\u002Fexternal exposure\n- auth前に到達可能か\n- confidentiality \u002F integrity \u002F availability impact\n- privilege required\n- affected data \u002F tenant scope\n- fix\u002Fpatch availability\n- workaround quality\n- regression\u002Fmigration risk\n- current target releaseとの距離\n\nproject固有priorityへ変換する。\n\n推奨概念:\n\n- **P0 \u002F Critical**: active exploitationまたは高確率で直接exposed、即時対応。必要なら現在sprintを中断しpatch release。\n- **P1 \u002F High**: reachableで重大impact、fix available。current releaseのblocking候補。\n- **P2 \u002F Medium**: 条件付きreachableまたはimpact限定。計画ticketとして近いreleaseへ。\n- **P3 \u002F Low**: non-reachable\u002Fdefense-in-depth。dependency hygieneとして処理。\n\nCVSSが高いだけでP0にしない。逆にCVSSが中程度でもproject exposureが高ければ優先度を上げる。\n\n## 4. Response workflow\n\nmeaningful advisoryを検出したら:\n\n1. affected versionを確認\n2. project reachabilityを確認\n3. exploit\u002Ffix情報を確認\n4. priority決定\n5. GitHub Issueを日本語で作成\u002F更新\n6. target releaseを決定\n7. isolated ticket branchで修正\n8. focused + integration security verification\n9.必要ならrelease gateへ追加\n10. advisory sourceと判断根拠をIssue\u002FADRへ残す\n\n緊急patchでは `release-x-y-z` のpatch versionを切ることを許可する。\n\n## 5. Automated security checks\n\nprojectに適切なら初期化時に導入・修復する。\n\n候補:\n\n- dependency vulnerability scan\n- dependency review on PR\n- code scanning \u002F SAST\n- secret scanning\n- container\u002Fimage scanning\n- SBOM generation\n- license\u002Fsecurity policy checks\n\nただし大量のfalse positiveをblockingにしてsignalを破壊しない。blocking\u002Fnon-blockingはproject riskに合わせて明示する。\n\n## 6. Security gate\n\nsecurity-related ticketは通常quality gateに加えて:\n\n- exploit\u002Freproduction条件の確認\n- vulnerable pathが修正後に閉じていること\n- regression test\n- dependency\u002Fversion resolution確認\n- production artifactにfixed versionが入ること\n- workaroundを入れた場合の撤去条件\n\nを検証する。\n\n## 7. Re-evaluation\n\nframework\u002Fruntime major\u002Fminor update、security policy変更、exposure変更、新しいexternal service追加時はsecurity profileを再評価する。\n","# Security Maintenance\n\nsecurity updateは単純なCVSS順ではなく、projectへの実到達可能性とrelease riskまで含めて優先順位を付ける。\n\n未知のsource vulnerability探索は `security-audit` が所有する。そこで `confirmed` になったfindingは本Skillへhandoffし、advisoryと同じproject-aware priority \u002F remediation \u002F release workflowへ統合する。`needs_validation` をconfirmed vulnerabilityとしてpriority化しない。\n\n## 1. Source priority\n\n初期化時および継続maintenance時に、実際に使用しているversionを基準に次を確認する。\n\n1. framework\u002Fruntime\u002FSDK official security advisories\n2. official release notes \u002F security announcements\n3. language\u002Fpackage ecosystem official advisory source\n4. GitHub Security Advisories \u002F dependency alerts\n5. maintainer issue \u002F patch release information\n6. trusted secondary source\n\n一般ニュースやSNSだけをsecurity SoTにしない。\n\n## 2. Inventory\n\n最低限把握する:\n\n- direct dependencies\n- security-sensitive transitive dependencies\n- framework\u002Fruntime\u002FSDK versions\n- container\u002Fbase image\n- OS\u002Fruntime packages when relevant\n- build\u002Fdeploy toolchain\n- externally exposed services\u002Fendpoints\n- auth\u002Fsession\u002Fcrypto\u002Fstorage\u002Fnetwork boundaries\n\nlockfileやgenerated SBOM等、再現可能なinventoryを優先する。\n\n## 3. Prioritization\n\nseverityだけで決めない。最低限次を評価する。\n\n- advisory severity \u002F CVSS等\n- exploitability \u002F exploit maturity\n- projectでvulnerable pathがreachableか\n- internet\u002Fexternal exposure\n- auth前に到達可能か\n- confidentiality \u002F integrity \u002F availability impact\n- privilege required\n- affected data \u002F tenant scope\n- fix\u002Fpatch availability\n- workaround quality\n- regression\u002Fmigration risk\n- current target releaseとの距離\n\nproject固有priorityへ変換する。\n\n推奨概念:\n\n- **P0 \u002F Critical**: active exploitationまたは高確率で直接exposed、即時対応。必要なら現在sprintを中断しpatch release。\n- **P1 \u002F High**: reachableで重大impact、fix available。current releaseのblocking候補。\n- **P2 \u002F Medium**: 条件付きreachableまたはimpact限定。計画ticketとして近いreleaseへ。\n- **P3 \u002F Low**: non-reachable\u002Fdefense-in-depth。dependency hygieneとして処理。\n\nCVSSが高いだけでP0にしない。逆にCVSSが中程度でもproject exposureが高ければ優先度を上げる。\n\n## 4. Response workflow\n\nmeaningful advisoryを検出したら:\n\n1. affected versionを確認\n2. project reachabilityを確認\n3. exploit\u002Ffix情報を確認\n4. priority決定\n5. GitHub Issueを日本語で作成\u002F更新\n6. target releaseを決定\n7. isolated ticket branchで修正\n8. focused + integration security verification\n9.必要ならrelease gateへ追加\n10. advisory sourceと判断根拠をIssue\u002FADRへ残す\n\n緊急patchでは `release-x-y-z` のpatch versionを切ることを許可する。\n\n## 5. Automated security checks\n\nprojectに適切なら初期化時に導入・修復する。\n\n候補:\n\n- dependency vulnerability scan\n- dependency review on PR\n- code scanning \u002F SAST\n- secret scanning\n- container\u002Fimage scanning\n- SBOM generation\n- license\u002Fsecurity policy checks\n\nただし大量のfalse positiveをblockingにしてsignalを破壊しない。blocking\u002Fnon-blockingはproject riskに合わせて明示する。\n\n## 6. Security gate\n\nsecurity-related ticketは通常quality gateに加えて:\n\n- exploit\u002Freproduction条件の確認\n- vulnerable pathが修正後に閉じていること\n- regression test\n- dependency\u002Fversion resolution確認\n- production artifactにfixed versionが入ること\n- workaroundを入れた場合の撤去条件\n\nを検証する。\n\n## 7. Re-evaluation\n\nframework\u002Fruntime major\u002Fminor update、security policy変更、exposure変更、新しいexternal service追加時はsecurity profileを再評価する。\n",{"name":5,"description":7},"main","fae2dd6b4eb2a8c4744ff719f591e6e697efe4a4","skills\u002Fsecurity-maintenance",0,"https:\u002F\u002Fgithub.com\u002Frebuildup\u002Fproject-init","https:\u002F\u002Fgithub.com\u002Frebuildup","https:\u002F\u002Frebuildup.dev","jp 2007\r\nweb制作か映像制作、それにまつわるツールの制作をしている高専生","2026-11-13 16:51:04",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add rebuildup\u002Fproject-init --skill security-maintenance",{"tool":39,"command":40},"bunx","bunx skills add rebuildup\u002Fproject-init --skill security-maintenance",{"tool":42,"command":43},"pnpm","pnpm dlx skills add rebuildup\u002Fproject-init --skill security-maintenance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frebuildup\u002Fproject-init\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-maintenance\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7AB77SBZEANKTQWPK1A9YW5","worktree-workflow","current release-driven profileでWorktrunkをWSL\u002FLinux workspace lifecycle Practiceとして使い、Rust\u002FCargo worktreeのbuild-output isolation・cache reuse・cleanupを含め、同等以上のguaranteeを持つalternativeへのrefinementも判断する時に使用する。","https:\u002F\u002Fgithub.com\u002Frebuildup\u002Fproject-init\u002Fblob\u002Fmain\u002Fskills\u002Fworktree-workflow\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7AB74AK8FAJ98HBC7KK1648","skill-selection","projectの初期化や再整備で、どのAgent Skillを導入するかを決める時に使用する。必要な能力を判定し、project-initの能力一覧と候補記録、さらに外部の探索から候補を評価して、能力ごとに担当を決め、project-localに導入してlockと採否を記録する。","https:\u002F\u002Fgithub.com\u002Frebuildup\u002Fproject-init\u002Fblob\u002Fmain\u002Fskills\u002Fskill-selection\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7AB6YFYS2QF2D1YH4K1117G","security-audit","source codeから未知のsecurity invariant failureを能動的に探索し、coverageを明示しながら独立検証されたfindingへ変換する時に使用する。","https:\u002F\u002Fgithub.com\u002Frebuildup\u002Fproject-init\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7AB6QW54HQ8JTRADE6NQ52X","secrets-management","application \u002F serviceのenvironment secretをInfisical中心で設計・初期化・移行・検証する時に使用する。CLI-first、repository-controlled schema、Machine Identity、GitHub OIDC、agent least-privilege、secret-safe evidenceを扱う。","https:\u002F\u002Fgithub.com\u002Frebuildup\u002Fproject-init\u002Fblob\u002Fmain\u002Fskills\u002Fsecrets-management\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7AB6N6WC13K9E0BPAFXWNPH","sandbox-runtime","implementation worker用の独立sandboxを作成・検証し、macOS \u002F WSL\u002FLinux \u002F remote provider差を吸収する時に使用する。","https:\u002F\u002Fgithub.com\u002Frebuildup\u002Fproject-init\u002Fblob\u002Fmain\u002Fskills\u002Fsandbox-runtime\u002FSKILL.md",[],[],{"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":89,"publishedAt":19},"01M7AB6GX1Q8VQRA96T0CXF06Z","quality-gate","project固有のstack・framework・runtimeに合わせてquality gateと動作確認レベルを設計・実行・更新する時に使用する。","https:\u002F\u002Fgithub.com\u002Frebuildup\u002Fproject-init\u002Fblob\u002Fmain\u002Fskills\u002Fquality-gate\u002FSKILL.md",[],[]]