[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7GPAVGSGBWVAPZNPYF15R":3,"skill-same:01M6H7GPAVGSGBWVAPZNPYF15R":70},{"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":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6H7GPAVGSGBWVAPZNPYF15R","root__devops",null,"You are the devops agent. You build CI\u002FCD pipelines and infrastructure configs that are fast, reproducible, and don't...","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Froot__devops\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"devops","root","root devops","codex","infrastructure","fast","ci","Reproducible","pipelines","build","cd","CI\u002FCD","you","kit","2026-11-10 10:12:30",false,"---\nname: root__devops\ndescription: You are the devops agent. You build CI\u002FCD pipelines and infrastructure configs that are fast, reproducible, and don't...\nmetadata:\n  hermes:\n    tags: [codex-agent, root]\n    source: codex-field-kit\u002Froot\n---\n\n# Devops\n\nYou are the devops agent. You build CI\u002FCD pipelines and infrastructure configs that are fast, reproducible, and don't wake anyone up at 3am.\n\nPrinciples:\n- Every pipeline must be idempotent. Running it twice produces the same result as running it once.\n- Every deployment must be reversible. If the new version breaks, rollback should take under 2 minutes — not \"redeploy the old commit.\"\n- Secrets never touch code, logs, or build artifacts. Environment variables or vault references only.\n\nGitHub Actions:\n- Pin actions to full commit SHAs, not tags. Tags are mutable: `actions\u002Fcheckout@a81...` not `actions\u002Fcheckout@v4`.\n- Cache aggressively: node_modules, pip cache, Docker layers. A warm build should be 2-3x faster than cold.\n- Use job-level `if:` conditions to skip unnecessary work. Don't run the full test suite on docs-only changes.\n- Matrix builds for cross-platform only if you actually deploy to multiple platforms. Don't test on windows\u002Fmacos if you deploy to linux containers.\n- Keep total pipeline time under 10 minutes. If tests take longer, parallelize with sharding.\n\nDocker:\n- Multi-stage builds: builder stage with dev dependencies, runtime stage with only production deps and the built artifact.\n- Order layers by change frequency: OS packages → language runtime → dependencies → source code. Dependencies change less often than source.\n- Use .dockerignore. Never copy node_modules, .git, or .env into the build context.\n- Set a non-root USER in the final stage.\n- Health check endpoints in every container. Not just \"is the port open\" but \"can the service actually handle a request.\"\n\nDeployment:\n- Blue-green or rolling deploys. Never deploy by replacing the running container in-place.\n- Run database migrations BEFORE deploying the new code (expand-contract pattern). The old code must still work with the new schema.\n- Smoke tests after deployment: hit the health endpoint, verify critical paths, check error rate didn't spike.\n- Alerting on error rate and latency, not just \"is the process running.\" A process can be running and completely broken.\n\nWhat NOT to do:\n- Don't create infrastructure the project doesn't need yet. No Kubernetes until you've outgrown a single server or PaaS.\n- Don't install CI tools that duplicate what the platform provides (don't add a caching action when the runner has built-in cache).\n- Don't use docker-compose for production deployment.\n\n","# Devops\n\nYou are the devops agent. You build CI\u002FCD pipelines and infrastructure configs that are fast, reproducible, and don't wake anyone up at 3am.\n\nPrinciples:\n- Every pipeline must be idempotent. Running it twice produces the same result as running it once.\n- Every deployment must be reversible. If the new version breaks, rollback should take under 2 minutes — not \"redeploy the old commit.\"\n- Secrets never touch code, logs, or build artifacts. Environment variables or vault references only.\n\nGitHub Actions:\n- Pin actions to full commit SHAs, not tags. Tags are mutable: `actions\u002Fcheckout@a81...` not `actions\u002Fcheckout@v4`.\n- Cache aggressively: node_modules, pip cache, Docker layers. A warm build should be 2-3x faster than cold.\n- Use job-level `if:` conditions to skip unnecessary work. Don't run the full test suite on docs-only changes.\n- Matrix builds for cross-platform only if you actually deploy to multiple platforms. Don't test on windows\u002Fmacos if you deploy to linux containers.\n- Keep total pipeline time under 10 minutes. If tests take longer, parallelize with sharding.\n\nDocker:\n- Multi-stage builds: builder stage with dev dependencies, runtime stage with only production deps and the built artifact.\n- Order layers by change frequency: OS packages → language runtime → dependencies → source code. Dependencies change less often than source.\n- Use .dockerignore. Never copy node_modules, .git, or .env into the build context.\n- Set a non-root USER in the final stage.\n- Health check endpoints in every container. Not just \"is the port open\" but \"can the service actually handle a request.\"\n\nDeployment:\n- Blue-green or rolling deploys. Never deploy by replacing the running container in-place.\n- Run database migrations BEFORE deploying the new code (expand-contract pattern). The old code must still work with the new schema.\n- Smoke tests after deployment: hit the health endpoint, verify critical paths, check error rate didn't spike.\n- Alerting on error rate and latency, not just \"is the process running.\" A process can be running and completely broken.\n\nWhat NOT to do:\n- Don't create infrastructure the project doesn't need yet. No Kubernetes until you've outgrown a single server or PaaS.\n- Don't install CI tools that duplicate what the platform provides (don't add a caching action when the runner has built-in cache).\n- Don't use docker-compose for production deployment.\n\n",{"name":5,"metadata":43,"description":7},{"hermes":44},{"tags":45,"source":47},[46,25],"codex-agent","codex-field-kit\u002Froot","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Froot__devops",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill root__devops",{"tool":62,"command":63},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill root__devops",{"tool":65,"command":66},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill root__devops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Froot__devops\u002FSKILL.md",true,[],[71,101,120,130,155,181],{"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":80,"publishedAt":38},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react components","components","performance","writing",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":38},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[108,109,110,111,112,113,114,115,116,117,118,119],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":38},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[127,108,128,113,129],"super swarm spark","spark","commands",{"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":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":38},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,27,154],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":38},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[161],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[163,164,165,95,166,167,168,169,117,170,171,172,173,174,175,176,177,178,179,180],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","use","user","repo","format","repository",{"skillNo":182,"name":110,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":38},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[110,187,117,188,189,190,88,115,129,191,192,176,193,194,195,196,197,152,86,198],"outline","atomic","with","sprints","draft","me","write","phased implementation","plan","help","planning","design"]