[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M786GCT80YXHZRG20ZPQGHTY":3,"skill-same:01M786GCT80YXHZRG20ZPQGHTY":146},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M786GCT80YXHZRG20ZPQGHTY","code-review-skill",null,"Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C\u002FC++. Helps catch bugs, improve code quality, and give constructive feedback. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, checking code quality, finding bugs, giving feedback on code.","chenziyang110\u002Flaunchdeck","chenziyang110","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43693913?v=4","01M7863EBWK1D0P6A29YGEMAS4","Robin11","01M7863ECM1VB6RXDMHTW90D2T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"code-review-skill\"\ndescription: \"Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C\u002FC++.\nHelps catch bugs, improve code quality, and give constructive feedback.\nUse when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes,\nestablishing review standards, mentoring developers, architecture reviews, security audits,\nchecking code quality, finding bugs, giving feedback on code.\n\"\ncompatibility: \"Requires spec-kit project structure with .specify\u002F directory\"\nmetadata:\n  author: \"github-spec-kit\"\n  source: \"templates\u002Fpassive-skills\u002Fcode-review-skill\u002FSKILL.md\"\n---\n\n\n# Code Review Excellence\n\nTransform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.\n\n## When to Use This Skill\n\n- Reviewing pull requests and code changes\n- Establishing code review standards for teams\n- Mentoring junior developers through reviews\n- Conducting architecture reviews\n- Creating review checklists and guidelines\n- Improving team collaboration\n- Reducing code review cycle time\n- Maintaining code quality standards\n\n## Core Principles\n\n### 1. The Review Mindset\n\n**Goals of Code Review:**\n- Catch bugs and edge cases\n- Ensure code maintainability\n- Share knowledge across team\n- Enforce coding standards\n- Improve design and architecture\n- Build team culture\n\n**Not the Goals:**\n- Show off knowledge\n- Nitpick formatting (use linters)\n- Block progress unnecessarily\n- Rewrite to your preference\n\n### 2. Effective Feedback\n\n**Good Feedback is:**\n- Specific and actionable\n- Educational, not judgmental\n- Focused on the code, not the person\n- Balanced (praise good work too)\n- Prioritized (critical vs nice-to-have)\n\n```markdown\n❌ Bad: \"This is wrong.\"\n✅ Good: \"This could cause a race condition when multiple users\n         access simultaneously. Consider using a mutex here.\"\n\n❌ Bad: \"Why didn't you use X pattern?\"\n✅ Good: \"Have you considered the Repository pattern? It would\n         make this easier to test. Here's an example: [link]\"\n\n❌ Bad: \"Rename this variable.\"\n✅ Good: \"[nit] Consider `userCount` instead of `uc` for\n         clarity. Not blocking if you prefer to keep it.\"\n```\n\n### 3. Review Scope\n\n**What to Review:**\n- Logic correctness and edge cases\n- Security vulnerabilities\n- Performance implications\n- Test coverage and quality\n- Error handling\n- Documentation and comments\n- API design and naming\n- Architectural fit\n\n**What Not to Review Manually:**\n- Code formatting (use Prettier, Black, etc.)\n- Import organization\n- Linting violations\n- Simple typos\n\n## Review Process\n\n### Phase 1: Context Gathering (2-3 minutes)\n\nBefore diving into code, understand:\n1. Read PR description and linked issue\n2. Check PR size (>400 lines? Ask to split)\n3. Review CI\u002FCD status (tests passing?)\n4. Understand the business requirement\n5. Note any relevant architectural decisions\n\n### Phase 2: High-Level Review (5-10 minutes)\n\n1. **Architecture & Design** - Does the solution fit the problem?\n   - For significant changes, consult [Architecture Review Guide](reference\u002Farchitecture-review-guide.md)\n   - Check: SOLID principles, coupling\u002Fcohesion, anti-patterns\n2. **Performance Assessment** - Are there performance concerns?\n   - For performance-critical code, consult [Performance Review Guide](reference\u002Fperformance-review-guide.md)\n   - Check: Algorithm complexity, N+1 queries, memory usage\n3. **File Organization** - Are new files in the right places?\n4. **Testing Strategy** - Are there tests covering edge cases?\n\n### Phase 3: Line-by-Line Review (10-20 minutes)\n\nFor each file, check:\n- **Logic & Correctness** - Edge cases, off-by-one, null checks, race conditions\n- **Security** - Input validation, injection risks, XSS, sensitive data\n- **Performance** - N+1 queries, unnecessary loops, memory leaks\n- **Maintainability** - Clear names, single responsibility, comments\n\n### Phase 4: Summary & Decision (2-3 minutes)\n\n1. Summarize key concerns\n2. Highlight what you liked\n3. Make clear decision:\n   - ✅ Approve\n   - 💬 Comment (minor suggestions)\n   - 🔄 Request Changes (must address)\n4. Offer to pair if complex\n\n## Review Techniques\n\n### Technique 1: The Checklist Method\n\nUse checklists for consistent reviews. See [Security Review Guide](reference\u002Fsecurity-review-guide.md) for comprehensive security checklist.\n\n### Technique 2: The Question Approach\n\nInstead of stating problems, ask questions:\n\n```markdown\n❌ \"This will fail if the list is empty.\"\n✅ \"What happens if `items` is an empty array?\"\n\n❌ \"You need error handling here.\"\n✅ \"How should this behave if the API call fails?\"\n```\n\n### Technique 3: Suggest, Don't Command\n\nUse collaborative language:\n\n```markdown\n❌ \"You must change this to use async\u002Fawait\"\n✅ \"Suggestion: async\u002Fawait might make this more readable. What do you think?\"\n\n❌ \"Extract this into a function\"\n✅ \"This logic appears in 3 places. Would it make sense to extract it?\"\n```\n\n### Technique 4: Differentiate Severity\n\nUse labels to indicate priority:\n\n- 🔴 `[blocking]` - Must fix before merge\n- 🟡 `[important]` - Should fix, discuss if disagree\n- 🟢 `[nit]` - Nice to have, not blocking\n- 💡 `[suggestion]` - Alternative approach to consider\n- 📚 `[learning]` - Educational comment, no action needed\n- 🎉 `[praise]` - Good work, keep it up!\n\n## Language-Specific Guides\n\n根据审查的代码语言，查阅对应的详细指南：\n\n| Language\u002FFramework | Reference File | Key Topics |\n|-------------------|----------------|------------|\n| **React** | [React Guide](reference\u002Freact.md) | Hooks, useEffect, React 19 Actions, RSC, Suspense, TanStack Query v5 |\n| **Vue 3** | [Vue Guide](reference\u002Fvue.md) | Composition API, 响应性系统, Props\u002FEmits, Watchers, Composables |\n| **Rust** | [Rust Guide](reference\u002Frust.md) | 所有权\u002F借用, Unsafe 审查, 异步代码, 错误处理 |\n| **TypeScript** | [TypeScript Guide](reference\u002Ftypescript.md) | 类型安全, async\u002Fawait, 不可变性 |\n| **Python** | [Python Guide](reference\u002Fpython.md) | 可变默认参数, 异常处理, 类属性 |\n| **Java** | [Java Guide](reference\u002Fjava.md) | Java 17\u002F21 新特性, Spring Boot 3, 虚拟线程, Stream\u002FOptional |\n| **Go** | [Go Guide](reference\u002Fgo.md) | 错误处理, goroutine\u002Fchannel, context, 接口设计 |\n| **C** | [C Guide](reference\u002Fc.md) | 指针\u002F缓冲区, 内存安全, UB, 错误处理 |\n| **C++** | [C++ Guide](reference\u002Fcpp.md) | RAII, 生命周期, Rule of 0\u002F3\u002F5, 异常安全 |\n| **CSS\u002FLess\u002FSass** | [CSS Guide](reference\u002Fcss-less-sass.md) | 变量规范, !important, 性能优化, 响应式, 兼容性 |\n| **Qt** | [Qt Guide](reference\u002Fqt.md) | 对象模型, 信号\u002F槽, 内存管理, 线程安全, 性能 |\n\n## Additional Resources\n\n- [Architecture Review Guide](reference\u002Farchitecture-review-guide.md) - 架构设计审查指南（SOLID、反模式、耦合度）\n- [Performance Review Guide](reference\u002Fperformance-review-guide.md) - 性能审查指南（Web Vitals、N+1、复杂度）\n- [Common Bugs Checklist](reference\u002Fcommon-bugs-checklist.md) - 按语言分类的常见错误清单\n- [Security Review Guide](reference\u002Fsecurity-review-guide.md) - 安全审查指南\n- [Code Review Best Practices](reference\u002Fcode-review-best-practices.md) - 代码审查最佳实践\n- [PR Review Template](assets\u002Fpr-review-template.md) - PR 审查评论模板\n- [Review Checklist](assets\u002Freview-checklist.md) - 快速参考清单\n","# Code Review Excellence\n\nTransform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.\n\n## When to Use This Skill\n\n- Reviewing pull requests and code changes\n- Establishing code review standards for teams\n- Mentoring junior developers through reviews\n- Conducting architecture reviews\n- Creating review checklists and guidelines\n- Improving team collaboration\n- Reducing code review cycle time\n- Maintaining code quality standards\n\n## Core Principles\n\n### 1. The Review Mindset\n\n**Goals of Code Review:**\n- Catch bugs and edge cases\n- Ensure code maintainability\n- Share knowledge across team\n- Enforce coding standards\n- Improve design and architecture\n- Build team culture\n\n**Not the Goals:**\n- Show off knowledge\n- Nitpick formatting (use linters)\n- Block progress unnecessarily\n- Rewrite to your preference\n\n### 2. Effective Feedback\n\n**Good Feedback is:**\n- Specific and actionable\n- Educational, not judgmental\n- Focused on the code, not the person\n- Balanced (praise good work too)\n- Prioritized (critical vs nice-to-have)\n\n```markdown\n❌ Bad: \"This is wrong.\"\n✅ Good: \"This could cause a race condition when multiple users\n         access simultaneously. Consider using a mutex here.\"\n\n❌ Bad: \"Why didn't you use X pattern?\"\n✅ Good: \"Have you considered the Repository pattern? It would\n         make this easier to test. Here's an example: [link]\"\n\n❌ Bad: \"Rename this variable.\"\n✅ Good: \"[nit] Consider `userCount` instead of `uc` for\n         clarity. Not blocking if you prefer to keep it.\"\n```\n\n### 3. Review Scope\n\n**What to Review:**\n- Logic correctness and edge cases\n- Security vulnerabilities\n- Performance implications\n- Test coverage and quality\n- Error handling\n- Documentation and comments\n- API design and naming\n- Architectural fit\n\n**What Not to Review Manually:**\n- Code formatting (use Prettier, Black, etc.)\n- Import organization\n- Linting violations\n- Simple typos\n\n## Review Process\n\n### Phase 1: Context Gathering (2-3 minutes)\n\nBefore diving into code, understand:\n1. Read PR description and linked issue\n2. Check PR size (>400 lines? Ask to split)\n3. Review CI\u002FCD status (tests passing?)\n4. Understand the business requirement\n5. Note any relevant architectural decisions\n\n### Phase 2: High-Level Review (5-10 minutes)\n\n1. **Architecture & Design** - Does the solution fit the problem?\n   - For significant changes, consult [Architecture Review Guide](reference\u002Farchitecture-review-guide.md)\n   - Check: SOLID principles, coupling\u002Fcohesion, anti-patterns\n2. **Performance Assessment** - Are there performance concerns?\n   - For performance-critical code, consult [Performance Review Guide](reference\u002Fperformance-review-guide.md)\n   - Check: Algorithm complexity, N+1 queries, memory usage\n3. **File Organization** - Are new files in the right places?\n4. **Testing Strategy** - Are there tests covering edge cases?\n\n### Phase 3: Line-by-Line Review (10-20 minutes)\n\nFor each file, check:\n- **Logic & Correctness** - Edge cases, off-by-one, null checks, race conditions\n- **Security** - Input validation, injection risks, XSS, sensitive data\n- **Performance** - N+1 queries, unnecessary loops, memory leaks\n- **Maintainability** - Clear names, single responsibility, comments\n\n### Phase 4: Summary & Decision (2-3 minutes)\n\n1. Summarize key concerns\n2. Highlight what you liked\n3. Make clear decision:\n   - ✅ Approve\n   - 💬 Comment (minor suggestions)\n   - 🔄 Request Changes (must address)\n4. Offer to pair if complex\n\n## Review Techniques\n\n### Technique 1: The Checklist Method\n\nUse checklists for consistent reviews. See [Security Review Guide](reference\u002Fsecurity-review-guide.md) for comprehensive security checklist.\n\n### Technique 2: The Question Approach\n\nInstead of stating problems, ask questions:\n\n```markdown\n❌ \"This will fail if the list is empty.\"\n✅ \"What happens if `items` is an empty array?\"\n\n❌ \"You need error handling here.\"\n✅ \"How should this behave if the API call fails?\"\n```\n\n### Technique 3: Suggest, Don't Command\n\nUse collaborative language:\n\n```markdown\n❌ \"You must change this to use async\u002Fawait\"\n✅ \"Suggestion: async\u002Fawait might make this more readable. What do you think?\"\n\n❌ \"Extract this into a function\"\n✅ \"This logic appears in 3 places. Would it make sense to extract it?\"\n```\n\n### Technique 4: Differentiate Severity\n\nUse labels to indicate priority:\n\n- 🔴 `[blocking]` - Must fix before merge\n- 🟡 `[important]` - Should fix, discuss if disagree\n- 🟢 `[nit]` - Nice to have, not blocking\n- 💡 `[suggestion]` - Alternative approach to consider\n- 📚 `[learning]` - Educational comment, no action needed\n- 🎉 `[praise]` - Good work, keep it up!\n\n## Language-Specific Guides\n\n根据审查的代码语言，查阅对应的详细指南：\n\n| Language\u002FFramework | Reference File | Key Topics |\n|-------------------|----------------|------------|\n| **React** | [React Guide](reference\u002Freact.md) | Hooks, useEffect, React 19 Actions, RSC, Suspense, TanStack Query v5 |\n| **Vue 3** | [Vue Guide](reference\u002Fvue.md) | Composition API, 响应性系统, Props\u002FEmits, Watchers, Composables |\n| **Rust** | [Rust Guide](reference\u002Frust.md) | 所有权\u002F借用, Unsafe 审查, 异步代码, 错误处理 |\n| **TypeScript** | [TypeScript Guide](reference\u002Ftypescript.md) | 类型安全, async\u002Fawait, 不可变性 |\n| **Python** | [Python Guide](reference\u002Fpython.md) | 可变默认参数, 异常处理, 类属性 |\n| **Java** | [Java Guide](reference\u002Fjava.md) | Java 17\u002F21 新特性, Spring Boot 3, 虚拟线程, Stream\u002FOptional |\n| **Go** | [Go Guide](reference\u002Fgo.md) | 错误处理, goroutine\u002Fchannel, context, 接口设计 |\n| **C** | [C Guide](reference\u002Fc.md) | 指针\u002F缓冲区, 内存安全, UB, 错误处理 |\n| **C++** | [C++ Guide](reference\u002Fcpp.md) | RAII, 生命周期, Rule of 0\u002F3\u002F5, 异常安全 |\n| **CSS\u002FLess\u002FSass** | [CSS Guide](reference\u002Fcss-less-sass.md) | 变量规范, !important, 性能优化, 响应式, 兼容性 |\n| **Qt** | [Qt Guide](reference\u002Fqt.md) | 对象模型, 信号\u002F槽, 内存管理, 线程安全, 性能 |\n\n## Additional Resources\n\n- [Architecture Review Guide](reference\u002Farchitecture-review-guide.md) - 架构设计审查指南（SOLID、反模式、耦合度）\n- [Performance Review Guide](reference\u002Fperformance-review-guide.md) - 性能审查指南（Web Vitals、N+1、复杂度）\n- [Common Bugs Checklist](reference\u002Fcommon-bugs-checklist.md) - 按语言分类的常见错误清单\n- [Security Review Guide](reference\u002Fsecurity-review-guide.md) - 安全审查指南\n- [Code Review Best Practices](reference\u002Fcode-review-best-practices.md) - 代码审查最佳实践\n- [PR Review Template](assets\u002Fpr-review-template.md) - PR 审查评论模板\n- [Review Checklist](assets\u002Freview-checklist.md) - 快速参考清单\n",{"name":5,"metadata":25,"description":28,"compatibility":29},{"author":26,"source":27},"github-spec-kit","templates\u002Fpassive-skills\u002Fcode-review-skill\u002FSKILL.md","Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C\u002FC++. Helps catch bugs, improve code quality, and give constructive feedback. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, checking code quality, finding bugs, giving feedback on code. ","Requires spec-kit project structure with .specify\u002F directory","main","021f5cbe02157229460a577e9a585f2da6d78cb0",".codex\u002Fskills\u002Fcode-review-skill","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck","https:\u002F\u002Fgithub.com\u002Fchenziyang110","2026-08-07 18:10:54",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add chenziyang110\u002Flaunchdeck --skill code-review-skill",{"tool":42,"command":43},"bunx","bunx skills add chenziyang110\u002Flaunchdeck --skill code-review-skill",{"tool":45,"command":46},"pnpm","pnpm dlx skills add chenziyang110\u002Flaunchdeck --skill code-review-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002FSKILL.md",true,[50,56,62,66,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},".gitignore","OTHER","其他",189,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002F.gitignore",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"assets\u002Fpr-review-template.md","ASSET","资产文件",1930,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Fassets\u002Fpr-review-template.md",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"assets\u002Freview-checklist.md",2791,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Fassets\u002Freview-checklist.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"CONTRIBUTING.md","REFERENCE","参考文档",7695,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002FCONTRIBUTING.md",{"path":73,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":16},"LICENSE","许可证",1063,{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"reference\u002Farchitecture-review-guide.md",15291,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Farchitecture-review-guide.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"reference\u002Fc.md",5582,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fc.md",{"path":85,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":86,"sourceHtmlUrl":87},"reference\u002Fcode-review-best-practices.md",3795,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fcode-review-best-practices.md",{"path":89,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":90,"sourceHtmlUrl":91},"reference\u002Fcommon-bugs-checklist.md",31955,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fcommon-bugs-checklist.md",{"path":93,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":94,"sourceHtmlUrl":95},"reference\u002Fcpp.md",7667,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fcpp.md",{"path":97,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":98,"sourceHtmlUrl":99},"reference\u002Fcss-less-sass.md",13113,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fcss-less-sass.md",{"path":101,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":102,"sourceHtmlUrl":103},"reference\u002Fgo.md",20279,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fgo.md",{"path":105,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":106,"sourceHtmlUrl":107},"reference\u002Fjava.md",10201,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fjava.md",{"path":109,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":110,"sourceHtmlUrl":111},"reference\u002Fperformance-review-guide.md",17573,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fperformance-review-guide.md",{"path":113,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":114,"sourceHtmlUrl":115},"reference\u002Fpython.md",24347,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fpython.md",{"path":117,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":118,"sourceHtmlUrl":119},"reference\u002Fqt.md",6153,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fqt.md",{"path":121,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":122,"sourceHtmlUrl":123},"reference\u002Freact.md",21979,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Freact.md",{"path":125,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":126,"sourceHtmlUrl":127},"reference\u002Frust.md",21030,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Frust.md",{"path":129,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":130,"sourceHtmlUrl":131},"reference\u002Fsecurity-review-guide.md",6836,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fsecurity-review-guide.md",{"path":133,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":134,"sourceHtmlUrl":135},"reference\u002Ftypescript.md",12883,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Ftypescript.md",{"path":137,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":138,"sourceHtmlUrl":139},"reference\u002Fvue.md",20499,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Freference\u002Fvue.md",{"path":141,"resourceType":142,"resourceTypeDesc":143,"sizeBytes":144,"sourceHtmlUrl":145},"scripts\u002Fpr-analyzer.py","SCRIPT","脚本",11213,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcode-review-skill\u002Fscripts\u002Fpr-analyzer.py",[147,154,160,166,173,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":20},"01M7875F3HQ1GF5F6BR36KY3JE","launchdeck-agent","Codex host adapter contract fixture for Launchdeck.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fagent-hosts\u002Fcodex\u002Fskill\u002FSKILL.md",[],[],{"skillNo":155,"name":149,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":20},"01M7875DV2DQR33K1NFJHKAMZP","Claude host adapter contract fixture for Launchdeck.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fagent-hosts\u002Fclaude\u002Fskill\u002FSKILL.md",[],[],{"skillNo":161,"name":149,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":20},"01M78759JQ7A6FQ8KDQTNYS3X9","Use this skill aggressively for local project lifecycle operations even when the user does not mention Launchdeck: start this project, run the dev server, dev, build, test, restart service, stop service, show logs, inspect ports, port is occupied, clean cache; and when the user explicitly asks to configure this local project for Launchdeck or create or generate a project-adapted `.launchdeck.yml`, including 为这个项目生成 Launchdeck 配置. Do not use for ordinary code edits, docs-only work, general explanations, API design discussion, or production deployment unless the user also asks to operate or configure a local project or service.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Fagent\u002Finstaller-payload\u002Fskill\u002Flaunchdeck-agent\u002FSKILL.md",[],[],{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":20},"01M78753ZJQ7G2CZT1W1G8WRJV","zig-testing","Use ONLY when user explicitly requests Zig test code, built-in test runner configuration,\ntest failure diagnosis, or coverage for Zig projects.\n\nTriggers: \"write test zig\", \"zig test\", \"testing.allocator\", \"zig coverage\",\n\"comptime test\", \"zig expectError\", \"zig snapshot test\", \"zig fuzz\".\n\nDo NOT activate for: general Zig coding without test context, build.zig configuration\nfor non-test targets, Zig compiler errors, or Zig build system setup.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fzig-testing\u002FSKILL.md",[],[],{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":178,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":20},"01M78750JXY4Z5D5W1EX3PQ31Z","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":20},"01M7874X2T83EQQFRCEY5SJJVC","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fverification-before-completion\u002FSKILL.md",[],[]]