[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BXBCKXYXWM7EJDMCCGMRKH":3,"skill-same:01M6BXBCKXYXWM7EJDMCCGMRKH":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6BXBCKXYXWM7EJDMCCGMRKH","github-pr-review",null,"Use when reviewing GitHub pull requests with gh CLI - creates pending reviews with code suggestions, batches comments, and chooses appropriate event types (COMMENT\u002FAPPROVE\u002FREQUEST_CHANGES)","Tohuhono\u002FOberon","Tohuhono","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F135709951?v=4","01M6BXAYQ0F1T2E4Y2T5T1J4AH","01M6BXAYVMYXSWAB9DGD0K3HXY",23,"MIT","https:\u002F\u002Fgithub.com\u002FTohuhono\u002FOberon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgithub-pr-review\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"github","github pr review","pr review","pr","review","github pr","gh cli","when","request","pending","batches","reviews","event","types","use","gh","pull","code","pull requests","cli","2026-11-10 10:12:30",false,"---\nname: github-pr-review\ndescription:\n  Use when reviewing GitHub pull requests with gh CLI - creates pending reviews with code\n  suggestions, batches comments, and chooses appropriate event types\n  (COMMENT\u002FAPPROVE\u002FREQUEST_CHANGES)\n---\n\n# GitHub PR Review\n\n## Overview\n\nWorkflow for reviewing GitHub pull requests using `gh api` to create pending reviews with code\nsuggestions. **Always use pending reviews to batch comments, even under time pressure.**\n\n## When to Use\n\n- Reviewing pull requests\n- Adding code suggestions to PRs\n- Posting review comments with the gh CLI\n\n## Core Workflow\n\n**REQUIRED STEPS (do not skip):**\n\n1. **Draft the review** - Analyze PR and prepare all comments\n2. **Post the review**\n\n### Technical Workflow\n\n````bash\n# Step 1: Create PENDING review (no event field)\ngh api repos\u002F:owner\u002F:repo\u002Fpulls\u002F\u003CPR_NUMBER>\u002Freviews \\\n  -X POST \\\n  -f commit_id=\"\u003CCOMMIT_SHA>\" \\\n  -f 'comments[][path]=path\u002Fto\u002Ffile.ts' \\\n  -F 'comments[][line]=\u003CLINE_NUMBER>' \\\n  -f 'comments[][side]=RIGHT' \\\n  -f 'comments[][body]=Comment text\n\n```suggestion\n\u002F\u002F suggested code here\n````\n\nAdditional explanation...' \\\n--jq '{id, state}'\n\n# Returns: {\"id\": \u003CREVIEW_ID>, \"state\": \"PENDING\"}\n\n# Step 2: Submit the pending review\n\ngh api repos\u002F:owner\u002F:repo\u002Fpulls\u002F\u003CPR_NUMBER>\u002Freviews\u002F\u003CREVIEW_ID>\u002Fevents \\\n-X POST \\\n-f event=\"COMMENT\" \\\n-f body=\"Optional overall review message\"\n\n````\n\n## Event Types\n\nChoose the appropriate event type when submitting:\n\n| Event Type | When to Use | Example Situations |\n|------------|-------------|-------------------|\n| `APPROVE` | Non-blocking suggestions, PR is ready to merge | Minor style improvements, optional refactoring |\n| `REQUEST_CHANGES` | Blocking issues that must be fixed | Security vulnerabilities, bugs, failing tests |\n| `COMMENT` | Neutral feedback, questions | Asking for clarification, neutral observations |\n\n## Quick Reference\n\n### Getting Prerequisites\n\n```bash\n# Get commit SHA\ngh pr view \u003CPR_NUMBER> --json commits --jq '.commits[-1].oid'\n\n# Repository info (usually auto-detected by gh)\ngh repo view --json owner,name\n````\n\n### Required Parameters\n\n- `commit_id`: Latest commit SHA from the PR\n- `comments[][path]`: File path relative to repo root\n- `comments[][line]`: End line number (use `-F` for numbers)\n- `comments[][side]`: Use `RIGHT` for added\u002Fmodified lines (most common), `LEFT` for deleted lines\n- `comments[][body]`: Comment text with optional ```suggestion block\n\n### Optional Parameters\n\n- `comments[][start_line]`: For multi-line code suggestions (use `-F`)\n- `event`: Omit for PENDING, or use `COMMENT`\u002F`APPROVE`\u002F`REQUEST_CHANGES`\n\n### Syntax Rules\n\n✅ **DO:**\n\n- Use single quotes around parameters with `[]`: `'comments[][path]'`\n- Use `-f` for string values\n- Use `-F` for numeric values (line numbers)\n- Use triple backticks with `suggestion` identifier for code suggestions\n\n❌ **DON'T:**\n\n- Use double quotes around `comments[][]` parameters\n- Mix up `-f` and `-F` flags\n- Forget to get commit SHA first\n\n## Code Suggestions Format\n\n````bash\n-f 'comments[][body]=Your comment explaining the issue\n\n```suggestion\n\u002F\u002F The suggested code that will replace the specified line(s)\nconst fixed = \"like this\";\n````\n\nAdditional context or explanation after the suggestion.'\n\n``````\n\n**Important**: Code suggestions replace the entire line or line range. Make sure the suggested code is complete and correct.\n\n### Edge Case: Suggestions with Nested Code Blocks\n\nWhen suggesting changes to markdown files or documentation that contain triple backticks, use 4 backticks or tildes to prevent conflicts:\n\n`````markdown\n````suggestion\n```javascript\n\u002F\u002F Suggested code with nested backticks\nconst example = \"value\";\n``````\n\n```\n\n```\n\nOr use tildes:\n\n`````markdown\n````suggestion\n```javascript\nconst example = \"value\";\n````\n`````\n\n```\n\n```\n\n````\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Posting immediately under time pressure | Still create pending review first - can submit immediately after |\n| \"Only one comment so no need for pending\" | Use pending anyway - consistent workflow, allows adding more later |\n| Forgetting single quotes around `comments[][]` | Always quote: `'comments[][path]'` not `comments[][path]` |\n| Not getting commit SHA | Run `gh pr view \u003CNUMBER> --json commits --jq '.commits[-1].oid'` |\n| Using wrong event type | Security\u002Fbugs → REQUEST_CHANGES, Style → APPROVE, Questions → COMMENT |\n\n## Red Flags - You're About to Violate the Pattern\n\nStop if you're thinking:\n- \"User said ASAP so I'll skip pending review\"\n- \"Only one comment so I'll post directly\"\n- \"Time pressure means I should post immediately\"\n- \"I'll post this one now and batch the rest later\"\n\n**Why pending reviews?** Take the same time (2 API calls vs 1) but provide critical benefits:\n- Can add more comments if you find additional issues while writing the first\n- Can review your own comments before submitting\n- Consistent workflow regardless of urgency\n- Batches all comments into one notification for the PR author\n\n**Example**\n\n```bash\n# Create pending review with multiple comments\ngh api repos\u002F:owner\u002F:repo\u002Fpulls\u002F123\u002Freviews \\\n  -X POST \\\n  -f commit_id=\"abc123\" \\\n  -f 'comments[][path]=src\u002Fauth.ts' \\\n  -F 'comments[][line]=20' \\\n  -f 'comments[][side]=RIGHT' \\\n  -f 'comments[][body]=First issue...' \\\n  -f 'comments[][path]=src\u002Fauth.ts' \\\n  -F 'comments[][line]=35' \\\n  -f 'comments[][side]=RIGHT' \\\n  -f 'comments[][body]=Second issue...' \\\n  -f 'comments[][path]=tests\u002Fauth.test.ts' \\\n  -F 'comments[][line]=12' \\\n  -f 'comments[][side]=RIGHT' \\\n  -f 'comments[][body]=Third issue...' \\\n  --jq '{id, state}'\n\n# Submit with appropriate event type\ngh api repos\u002F:owner\u002F:repo\u002Fpulls\u002F123\u002Freviews\u002F\u003CREVIEW_ID>\u002Fevents \\\n  -X POST \\\n  -f event=\"REQUEST_CHANGES\" \\\n  -f body=\"Found 3 issues that need to be addressed before merging.\"\n````\n\n## Real-World Impact\n\n**Without this pattern:**\n\n- Multiple separate notifications spam the PR author\n- Can't batch feedback together\n- Easy to forget issues while reviewing\n- Inconsistent workflow based on perceived urgency\n\n**With this pattern:**\n\n- All feedback in one coherent review\n- PR author gets one notification with full context\n- Can refine comments before posting\n- Professional, organized reviews\n\n```\n\n```\n","# GitHub PR Review\n\n## Overview\n\nWorkflow for reviewing GitHub pull requests using `gh api` to create pending reviews with code\nsuggestions. **Always use pending reviews to batch comments, even under time pressure.**\n\n## When to Use\n\n- Reviewing pull requests\n- Adding code suggestions to PRs\n- Posting review comments with the gh CLI\n\n## Core Workflow\n\n**REQUIRED STEPS (do not skip):**\n\n1. **Draft the review** - Analyze PR and prepare all comments\n2. **Post the review**\n\n### Technical Workflow\n\n````bash\n# Step 1: Create PENDING review (no event field)\ngh api repos\u002F:owner\u002F:repo\u002Fpulls\u002F\u003CPR_NUMBER>\u002Freviews \\\n  -X POST \\\n  -f commit_id=\"\u003CCOMMIT_SHA>\" \\\n  -f 'comments[][path]=path\u002Fto\u002Ffile.ts' \\\n  -F 'comments[][line]=\u003CLINE_NUMBER>' \\\n  -f 'comments[][side]=RIGHT' \\\n  -f 'comments[][body]=Comment text\n\n```suggestion\n\u002F\u002F suggested code here\n````\n\nAdditional explanation...' \\\n--jq '{id, state}'\n\n# Returns: {\"id\": \u003CREVIEW_ID>, \"state\": \"PENDING\"}\n\n# Step 2: Submit the pending review\n\ngh api repos\u002F:owner\u002F:repo\u002Fpulls\u002F\u003CPR_NUMBER>\u002Freviews\u002F\u003CREVIEW_ID>\u002Fevents \\\n-X POST \\\n-f event=\"COMMENT\" \\\n-f body=\"Optional overall review message\"\n\n````\n\n## Event Types\n\nChoose the appropriate event type when submitting:\n\n| Event Type | When to Use | Example Situations |\n|------------|-------------|-------------------|\n| `APPROVE` | Non-blocking suggestions, PR is ready to merge | Minor style improvements, optional refactoring |\n| `REQUEST_CHANGES` | Blocking issues that must be fixed | Security vulnerabilities, bugs, failing tests |\n| `COMMENT` | Neutral feedback, questions | Asking for clarification, neutral observations |\n\n## Quick Reference\n\n### Getting Prerequisites\n\n```bash\n# Get commit SHA\ngh pr view \u003CPR_NUMBER> --json commits --jq '.commits[-1].oid'\n\n# Repository info (usually auto-detected by gh)\ngh repo view --json owner,name\n````\n\n### Required Parameters\n\n- `commit_id`: Latest commit SHA from the PR\n- `comments[][path]`: File path relative to repo root\n- `comments[][line]`: End line number (use `-F` for numbers)\n- `comments[][side]`: Use `RIGHT` for added\u002Fmodified lines (most common), `LEFT` for deleted lines\n- `comments[][body]`: Comment text with optional ```suggestion block\n\n### Optional Parameters\n\n- `comments[][start_line]`: For multi-line code suggestions (use `-F`)\n- `event`: Omit for PENDING, or use `COMMENT`\u002F`APPROVE`\u002F`REQUEST_CHANGES`\n\n### Syntax Rules\n\n✅ **DO:**\n\n- Use single quotes around parameters with `[]`: `'comments[][path]'`\n- Use `-f` for string values\n- Use `-F` for numeric values (line numbers)\n- Use triple backticks with `suggestion` identifier for code suggestions\n\n❌ **DON'T:**\n\n- Use double quotes around `comments[][]` parameters\n- Mix up `-f` and `-F` flags\n- Forget to get commit SHA first\n\n## Code Suggestions Format\n\n````bash\n-f 'comments[][body]=Your comment explaining the issue\n\n```suggestion\n\u002F\u002F The suggested code that will replace the specified line(s)\nconst fixed = \"like this\";\n````\n\nAdditional context or explanation after the suggestion.'\n\n``````\n\n**Important**: Code suggestions replace the entire line or line range. Make sure the suggested code is complete and correct.\n\n### Edge Case: Suggestions with Nested Code Blocks\n\nWhen suggesting changes to markdown files or documentation that contain triple backticks, use 4 backticks or tildes to prevent conflicts:\n\n`````markdown\n````suggestion\n```javascript\n\u002F\u002F Suggested code with nested backticks\nconst example = \"value\";\n``````\n\n```\n\n```\n\nOr use tildes:\n\n`````markdown\n````suggestion\n```javascript\nconst example = \"value\";\n````\n`````\n\n```\n\n```\n\n````\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Posting immediately under time pressure | Still create pending review first - can submit immediately after |\n| \"Only one comment so no need for pending\" | Use pending anyway - consistent workflow, allows adding more later |\n| Forgetting single quotes around `comments[][]` | Always quote: `'comments[][path]'` not `comments[][path]` |\n| Not getting commit SHA | Run `gh pr view \u003CNUMBER> --json commits --jq '.commits[-1].oid'` |\n| Using wrong event type | Security\u002Fbugs → REQUEST_CHANGES, Style → APPROVE, Questions → COMMENT |\n\n## Red Flags - You're About to Violate the Pattern\n\nStop if you're thinking:\n- \"User said ASAP so I'll skip pending review\"\n- \"Only one comment so I'll post directly\"\n- \"Time pressure means I should post immediately\"\n- \"I'll post this one now and batch the rest later\"\n\n**Why pending reviews?** Take the same time (2 API calls vs 1) but provide critical benefits:\n- Can add more comments if you find additional issues while writing the first\n- Can review your own comments before submitting\n- Consistent workflow regardless of urgency\n- Batches all comments into one notification for the PR author\n\n**Example**\n\n```bash\n# Create pending review with multiple comments\ngh api repos\u002F:owner\u002F:repo\u002Fpulls\u002F123\u002Freviews \\\n  -X POST \\\n  -f commit_id=\"abc123\" \\\n  -f 'comments[][path]=src\u002Fauth.ts' \\\n  -F 'comments[][line]=20' \\\n  -f 'comments[][side]=RIGHT' \\\n  -f 'comments[][body]=First issue...' \\\n  -f 'comments[][path]=src\u002Fauth.ts' \\\n  -F 'comments[][line]=35' \\\n  -f 'comments[][side]=RIGHT' \\\n  -f 'comments[][body]=Second issue...' \\\n  -f 'comments[][path]=tests\u002Fauth.test.ts' \\\n  -F 'comments[][line]=12' \\\n  -f 'comments[][side]=RIGHT' \\\n  -f 'comments[][body]=Third issue...' \\\n  --jq '{id, state}'\n\n# Submit with appropriate event type\ngh api repos\u002F:owner\u002F:repo\u002Fpulls\u002F123\u002Freviews\u002F\u003CREVIEW_ID>\u002Fevents \\\n  -X POST \\\n  -f event=\"REQUEST_CHANGES\" \\\n  -f body=\"Found 3 issues that need to be addressed before merging.\"\n````\n\n## Real-World Impact\n\n**Without this pattern:**\n\n- Multiple separate notifications spam the PR author\n- Can't batch feedback together\n- Easy to forget issues while reviewing\n- Inconsistent workflow based on perceived urgency\n\n**With this pattern:**\n\n- All feedback in one coherent review\n- PR author gets one notification with full context\n- Can refine comments before posting\n- Professional, organized reviews\n\n```\n\n```\n",{"name":5,"description":7},"main","14802e0b8d6e1798a47427c4aaff725758531e24",".agents\u002Fskills\u002Fgithub-pr-review",4,"https:\u002F\u002Fgithub.com\u002FTohuhono\u002FOberon","https:\u002F\u002Foberon-tohuhono.vercel.app","https:\u002F\u002Fgithub.com\u002FTohuhono","2026-11-10 16:26:11",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add Tohuhono\u002FOberon --skill github-pr-review",{"tool":57,"command":58},"bunx","bunx skills add Tohuhono\u002FOberon --skill github-pr-review",{"tool":60,"command":61},"pnpm","pnpm dlx skills add Tohuhono\u002FOberon --skill github-pr-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTohuhono\u002FOberon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgithub-pr-review\u002FSKILL.md",true,[65,71,75,79,83,87,91],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fagents\u002Freviewer.md","REFERENCE","参考文档",2252,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fnpm\u002Fvaayne-agent-kit\u002Fskills\u002Fspecs-dev\u002Freferences\u002Fagents\u002Freviewer.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fagents\u002Fworker.md",2272,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fnpm\u002Fvaayne-agent-kit\u002Fskills\u002Fspecs-dev\u002Freferences\u002Fagents\u002Fworker.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fgates.md",742,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fnpm\u002Fvaayne-agent-kit\u002Fskills\u002Fspecs-dev\u002Freferences\u002Fgates.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fhelp.md",1392,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fnpm\u002Fvaayne-agent-kit\u002Fskills\u002Fspecs-dev\u002Freferences\u002Fhelp.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Floop.md",4401,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fnpm\u002Fvaayne-agent-kit\u002Fskills\u002Fspecs-dev\u002Freferences\u002Floop.md",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Ftemplates\u002Fplan.md",1467,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fnpm\u002Fvaayne-agent-kit\u002Fskills\u002Fspecs-dev\u002Freferences\u002Ftemplates\u002Fplan.md",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Ftemplates\u002Ftasks.md",881,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fnpm\u002Fvaayne-agent-kit\u002Fskills\u002Fspecs-dev\u002Freferences\u002Ftemplates\u002Ftasks.md",[96,113,133,157,170,188],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":38},"01M716NHE5Y7QMMR5FZEY2D84S","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002FTohuhono\u002FOberon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[103,104,105,106,107,108,109,110,111,112],"wait what","wait","last","true","message","land","re","pitch","it","stop",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":38},"01M6BXBYKDEB19X2DVZWDDQ43N","to-tickets","Break a plan, spec, or conversation into tracer-bullet GitHub issues for Oberon, with category and state labels, sub-issues, and blocking relationships.","https:\u002F\u002Fgithub.com\u002FTohuhono\u002FOberon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[120,121,122,123,124,125,106,126,127,128,129,130,131,18,132],"to tickets","tickets","plan","labels","break","for","with","relationships","conversation","issues","state","github issues","spec",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":38},"01M6BXBTNJ43ZFWMKJRJX0Q51Y","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002FTohuhono\u002FOberon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[135,140,141,142,143,144,145,146,147,25,148,149,32,150,151,152,153,154,155,156],"green","test-first","test-driven","features","bugs","fix bugs","red","tests","build","red-green-refactor","fix","first","refactor","integration","integration tests","test","development",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":38},"01M6BXBKWFJFYVS7MZKYKNHS2Y","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002FTohuhono\u002FOberon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhandoff\u002FSKILL.md",[],[159,164,125,106,165,166,128,167,168,169],"session","next","compact","document","up","pick",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":38},"01M6BXBGFFK8E8H92GRKST59HG","grill-with-docs","A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.","https:\u002F\u002Fgithub.com\u002FTohuhono\u002FOberon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgrill-with-docs\u002FSKILL.md",[],[126,177,178,179,180,181,182,106,183,184,185,186,187,122],"grill","grill with docs","docs","design","go","which","as","interview","glossary","adr","sharpen",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":204,"publishedAt":38},"01M6BXB0ZGP9VZY05BE2S32Z4X","code-review","Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue\u002Fspec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".","https:\u002F\u002Fgithub.com\u002FTohuhono\u002FOberon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcode-review\u002FSKILL.md",[194,199],{"categoryNo":195,"categoryName":196,"taxonomyType":197,"taxonomyTypeDesc":198},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":200,"categoryName":201,"taxonomyType":202,"taxonomyTypeDesc":203},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[22,205,35,32,25,206,207,125,29,208,209,210,211,212,213,214,215,216,21,217,218,132],"code review","point","changes","progress","what the","reports","standards","repo","branch","work","parallel","coding standards","merge","commit"]