[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASMR6CFHG3JFPN1MP8CMYY":3,"skill-same:01M7ASMR6CFHG3JFPN1MP8CMYY":57},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7ASMR6CFHG3JFPN1MP8CMYY","ops-reliability",null,"Reviews PR diffs for reliability, operability, performance, and leftover concurrency hazards beyond race hunting. Use when analyze risk_class includes ops or concurrency, or when a PR adds dependencies, queues, retries, or hot-path work.","ozzycodes2\u002Fclaudellum","ozzycodes2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21285094?v=4","01M7ASJ57KTP519F96S4QGM7C5","Osniel Quintana","01M7ASJ589JS8S075AA92Y08S4",1,"MIT","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Freview\u002Fskills\u002Fops-reliability\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ops-reliability\ndescription: Reviews PR diffs for reliability, operability, performance, and leftover concurrency hazards beyond race hunting. Use when analyze risk_class includes ops or concurrency, or when a PR adds dependencies, queues, retries, or hot-path work.\nallowed-tools: Bash Read Grep Glob\n---\n\n# Ops & Reliability Review\n\nQuality Review pass covering taxonomy categories **8 Reliability & operability**, **10 Performance & scalability**, plus concurrency leftovers beyond the bug-finder's race focus (DLQ\u002Fpoison, async cancellation leftovers, ordering). Emits Conventional Comment findings in the bug-finder schema.\n\n## Inputs\n\n- **PR URL**: Full GitHub\u002FEnterprise PR URL\n- **OUTPUT_DIR** (optional): Defaults to private `mktemp -d`\n- **Analysis JSON** (optional): `$OUTPUT_DIR\u002Fpr-analysis-\u003CPR_NUMBER>.json`\n\n## Outputs\n\nWrites `$OUTPUT_DIR\u002Fops-reliability-\u003CPR_NUMBER>.json`:\n\n```json\n{\n  \"pr_number\": 123,\n  \"pass\": \"ops-reliability\",\n  \"findings\": [\n    {\n      \"severity\": \"critical|high|medium\",\n      \"label\": \"issue|suggestion|nitpick|question|thought|praise\",\n      \"decoration\": \"blocking|non-blocking|if-minor\",\n      \"path\": \"exact\u002Fpath\",\n      \"line\": 42,\n      \"title\": \"5-10 words\",\n      \"body\": \"explanation\",\n      \"suggestion\": \"concrete fix\",\n      \"suggested_change\": \"exact replacement for lines start_line..line, or omit\"\n    }\n  ]\n}\n```\n\n`suggested_change` posts as a committable GitHub suggestion. Emit it only\nwhen the fix is confined to the commented lines, you can reproduce the range\nverbatim from the diff, and it runs under ~10 lines; otherwise leave the prose\n`suggestion` alone. Most findings in this pass are design-level and will not\nqualify.\n\n## Step 0: Parse arguments\n\n```bash\nPR_URL=\"$1\"\nOUTPUT_DIR=\"${2:-$(mktemp -d -t pr-review-XXXXXX)}\"\nmkdir -p \"$OUTPUT_DIR\"\nPR_NUMBER=$(echo \"$PR_URL\" | grep -oE 'pull\u002F[0-9]+' | grep -oE '[0-9]+')\n```\n\n## Step 1: Load context (progressive disclosure)\n\n1. Read `references\u002Fanti-patterns.md`.\n2. Read this skill's `references\u002Fchecklist.md`.\n3. Optionally skim `shared\u002Fseverity-rubric.md`.\n4. If present, read analysis JSON for ops\u002Fhot-path hints.\n\n## Step 2: Load the PR diff\n\n`\u002Freview:review` captures the PR once into `$OUTPUT_DIR` and every pass shares\nit. Read `$OUTPUT_DIR\u002Fpr.diff` and `$OUTPUT_DIR\u002Fpr-view.json`; never write to\neither — the other passes are reading them. Fetch only when run standalone:\n\n```bash\nif [ ! -s \"$OUTPUT_DIR\u002Fpr.diff\" ]; then\n  gh pr diff \"$PR_URL\" > \"$OUTPUT_DIR\u002Fpr.diff\"\n  gh pr view \"$PR_URL\" --json title,body,files,additions,deletions,commits \\\n    > \"$OUTPUT_DIR\u002Fpr-view.json\"\nfi\n```\n\nFocus on clients\u002FHTTP calls, queues\u002Fconsumers, retries\u002Ftimeouts, caches, pagination, resource pools, metrics\u002Flogging on new paths.\n\n## Step 3: Review\n\nWalk checklist: failure modes → timeouts\u002Fretries\u002Fisolation → observability → performance → concurrency leftovers. Clean Code findings that obscure failure modes are **blocking regardless of module reach**. Name the resolving refactoring in `suggestion`.\n\nDo **not** re-litigate basic race\u002FNPE hunting (bug-finder owns that); focus on operational consequences and leftover concurrency classes listed in the checklist.\n\n## Step 4: Emit JSON\n\n```bash\njq -n \\\n  --argjson pr_number \"$PR_NUMBER\" \\\n  --arg pass \"ops-reliability\" \\\n  --argjson findings \"$FINDINGS_JSON\" \\\n  '{pr_number: $pr_number, pass: $pass, findings: $findings}' \\\n  > \"$OUTPUT_DIR\u002Fops-reliability-${PR_NUMBER}.json\"\n```\n\n## Notes\n\n- Standalone: `\u002Freview:ops-reliability \u003CPR_URL> [OUTPUT_DIR]`\n- Orchestrator runs when `ops` or `concurrency` ∈ `risk_class`\n","# Ops & Reliability Review\n\nQuality Review pass covering taxonomy categories **8 Reliability & operability**, **10 Performance & scalability**, plus concurrency leftovers beyond the bug-finder's race focus (DLQ\u002Fpoison, async cancellation leftovers, ordering). Emits Conventional Comment findings in the bug-finder schema.\n\n## Inputs\n\n- **PR URL**: Full GitHub\u002FEnterprise PR URL\n- **OUTPUT_DIR** (optional): Defaults to private `mktemp -d`\n- **Analysis JSON** (optional): `$OUTPUT_DIR\u002Fpr-analysis-\u003CPR_NUMBER>.json`\n\n## Outputs\n\nWrites `$OUTPUT_DIR\u002Fops-reliability-\u003CPR_NUMBER>.json`:\n\n```json\n{\n  \"pr_number\": 123,\n  \"pass\": \"ops-reliability\",\n  \"findings\": [\n    {\n      \"severity\": \"critical|high|medium\",\n      \"label\": \"issue|suggestion|nitpick|question|thought|praise\",\n      \"decoration\": \"blocking|non-blocking|if-minor\",\n      \"path\": \"exact\u002Fpath\",\n      \"line\": 42,\n      \"title\": \"5-10 words\",\n      \"body\": \"explanation\",\n      \"suggestion\": \"concrete fix\",\n      \"suggested_change\": \"exact replacement for lines start_line..line, or omit\"\n    }\n  ]\n}\n```\n\n`suggested_change` posts as a committable GitHub suggestion. Emit it only\nwhen the fix is confined to the commented lines, you can reproduce the range\nverbatim from the diff, and it runs under ~10 lines; otherwise leave the prose\n`suggestion` alone. Most findings in this pass are design-level and will not\nqualify.\n\n## Step 0: Parse arguments\n\n```bash\nPR_URL=\"$1\"\nOUTPUT_DIR=\"${2:-$(mktemp -d -t pr-review-XXXXXX)}\"\nmkdir -p \"$OUTPUT_DIR\"\nPR_NUMBER=$(echo \"$PR_URL\" | grep -oE 'pull\u002F[0-9]+' | grep -oE '[0-9]+')\n```\n\n## Step 1: Load context (progressive disclosure)\n\n1. Read `references\u002Fanti-patterns.md`.\n2. Read this skill's `references\u002Fchecklist.md`.\n3. Optionally skim `shared\u002Fseverity-rubric.md`.\n4. If present, read analysis JSON for ops\u002Fhot-path hints.\n\n## Step 2: Load the PR diff\n\n`\u002Freview:review` captures the PR once into `$OUTPUT_DIR` and every pass shares\nit. Read `$OUTPUT_DIR\u002Fpr.diff` and `$OUTPUT_DIR\u002Fpr-view.json`; never write to\neither — the other passes are reading them. Fetch only when run standalone:\n\n```bash\nif [ ! -s \"$OUTPUT_DIR\u002Fpr.diff\" ]; then\n  gh pr diff \"$PR_URL\" > \"$OUTPUT_DIR\u002Fpr.diff\"\n  gh pr view \"$PR_URL\" --json title,body,files,additions,deletions,commits \\\n    > \"$OUTPUT_DIR\u002Fpr-view.json\"\nfi\n```\n\nFocus on clients\u002FHTTP calls, queues\u002Fconsumers, retries\u002Ftimeouts, caches, pagination, resource pools, metrics\u002Flogging on new paths.\n\n## Step 3: Review\n\nWalk checklist: failure modes → timeouts\u002Fretries\u002Fisolation → observability → performance → concurrency leftovers. Clean Code findings that obscure failure modes are **blocking regardless of module reach**. Name the resolving refactoring in `suggestion`.\n\nDo **not** re-litigate basic race\u002FNPE hunting (bug-finder owns that); focus on operational consequences and leftover concurrency classes listed in the checklist.\n\n## Step 4: Emit JSON\n\n```bash\njq -n \\\n  --argjson pr_number \"$PR_NUMBER\" \\\n  --arg pass \"ops-reliability\" \\\n  --argjson findings \"$FINDINGS_JSON\" \\\n  '{pr_number: $pr_number, pass: $pass, findings: $findings}' \\\n  > \"$OUTPUT_DIR\u002Fops-reliability-${PR_NUMBER}.json\"\n```\n\n## Notes\n\n- Standalone: `\u002Freview:ops-reliability \u003CPR_URL> [OUTPUT_DIR]`\n- Orchestrator runs when `ops` or `concurrency` ∈ `risk_class`\n",{"name":5,"description":7,"allowed-tools":24},"Bash Read Grep Glob","main","a3f19bcc313571bff79dca391a83f9c4d38bb335","review\u002Fskills\u002Fops-reliability",0,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum","https:\u002F\u002Fgithub.com\u002Fozzycodes2","Software Engineer | Engineering Manager | AI whisperer | ☕Enjoyer","2026-11-14 04:50:11",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add ozzycodes2\u002Fclaudellum --skill ops-reliability",{"tool":39,"command":40},"bunx","bunx skills add ozzycodes2\u002Fclaudellum --skill ops-reliability",{"tool":42,"command":43},"pnpm","pnpm dlx skills add ozzycodes2\u002Fclaudellum --skill ops-reliability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Freview\u002Fskills\u002Fops-reliability\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fanti-patterns.md","REFERENCE","参考文档",1328,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Freview\u002Fskills\u002Fops-reliability\u002Freferences\u002Fanti-patterns.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fchecklist.md",3673,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Freview\u002Fskills\u002Fops-reliability\u002Freferences\u002Fchecklist.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7ASQB3CTKMKDNAXD9DCF1YC","writing-design-docs","Use when the user wants to write a problem-statement design doc, says \"let's plan a feature properly\" \u002F \"write a design doc\" \u002F \"I'm thinking about how to do X\" for a non-trivial X, or before committing to a non-obvious technical direction","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fwriting-design-docs\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7ASQ6JD4QRV5ZKK2QME401Y","write-doc","Use when the user asks to write or draft a README, ADR, runbook, tutorial, how-to, explanation, or reference doc, or a caller passes \"type ADR\" or \"type README\". Picks the type, fills a template, adds diagrams. RFCs and design docs belong to writing-design-docs.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fwrite-doc\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7ASQ1VWNVP1RE7M5D4G2QMG","review-doc","Use when the user asks to review, critique, score, grade, or \"how good is this doc\" for a Markdown doc or pasted text. Read-only. Scores it on the 20 Practical Prose dimensions and emits a findings table. Does not edit; fix-doc applies the findings next.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Freview-doc\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7ASPWST208JZNR7HF7J6KMV","fix-doc","Use when the user asks to fix, edit for prose quality, polish, tighten, humanize, or de-slop a Markdown doc or pasted text, or says \"make this read less AI\". Applies review-doc findings, generates flagged diagrams, lists substantive issues for the author, then runs the AI-tell pass last. Modifies the target.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Ffix-doc\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7ASPS6Y9ZGK9KCDHNPDR75A","create-slides","Use when the user asks for a slide deck, presentation, talk, or slides from a document, report, PR, notes, or topic. Builds one self-contained Machinify-branded HTML deck in a minimalist style, with headline-plus-visual slides, speaker notes, and every diagram drawn by architecture-design:create-diagram.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7ASPAKFY045KHR92Y4QFTWV","start-session","Open a Claude Code working session in a fresh, isolated git worktree, so the user can start a task with a single \u002Fstart-session \u003Cname>. Use at the START of a session when the user says \"start session\", \"start a worktree\", \"spin up a worktree for ABC-123\", \"begin work on \u003Cticket>\", or passes a name\u002Fticket to work under. Creates and ENTERS a worktree via the EnterWorktree tool (never `git worktree add`) under .claude\u002Fworktrees\u002F, named exactly after the argument, on a local branch `worktree-\u003Cargument>`. Reports what the worktree inherited (`.worktreeinclude` copies, symlinked node_modules) and whether its `.env` still points at the main checkout's stack. If the argument is a JIRA key (e.g. ABC-123, PROJ-1505), also loads that story with the Atlassian CLI (`acli`) when available and summarizes the implementation ask. Also renames the session to the argument (the same effect as `\u002Frename \u003CNAME>`) so it's easy to find in `\u002Fresume`. Then stops and waits — it sets up the workspace and context, it does not implement.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Fsession-mgmt\u002Fskills\u002Fstart-session\u002FSKILL.md",[],[]]