[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M786Z1TP0471R6EP4DH69JWV":3,"skill-same:01M786Z1TP0471R6EP4DH69JWV":148},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M786Z1TP0471R6EP4DH69JWV","code-review-excellence",null,"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.","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.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-review-excellence\ndescription: |\n  Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C\u002FC++.\n  Helps catch bugs, improve code quality, and give constructive feedback.\n  Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes,\n  establishing review standards, mentoring developers, architecture reviews, security audits,\n  checking code quality, finding bugs, giving feedback on code.\nallowed-tools:\n  - Read\n  - Grep\n  - Glob\n  - Bash      # 运行 lint\u002Ftest\u002Fbuild 命令验证代码质量\n  - WebFetch  # 查阅最新文档和最佳实践\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,"description":25,"allowed-tools":26},"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",[27,28,29,30,31],"Read","Grep","Glob","Bash","WebFetch","main","021f5cbe02157229460a577e9a585f2da6d78cb0",".specify\u002Ftemplates\u002Fpassive-skills\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":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add chenziyang110\u002Flaunchdeck --skill code-review-excellence",{"tool":44,"command":45},"bunx","bunx skills add chenziyang110\u002Flaunchdeck --skill code-review-excellence",{"tool":47,"command":48},"pnpm","pnpm dlx skills add chenziyang110\u002Flaunchdeck --skill code-review-excellence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002FSKILL.md",true,[52,58,64,68,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},".gitignore","OTHER","其他",189,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002F.gitignore",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002Fpr-review-template.md","ASSET","资产文件",1930,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Fassets\u002Fpr-review-template.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"assets\u002Freview-checklist.md",2791,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Fassets\u002Freview-checklist.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"CONTRIBUTING.md","REFERENCE","参考文档",7695,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002FCONTRIBUTING.md",{"path":75,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":16},"LICENSE","许可证",1063,{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"reference\u002Farchitecture-review-guide.md",15291,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Farchitecture-review-guide.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"reference\u002Fc.md",5582,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fc.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"reference\u002Fcode-review-best-practices.md",3795,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fcode-review-best-practices.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"reference\u002Fcommon-bugs-checklist.md",31955,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fcommon-bugs-checklist.md",{"path":95,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":96,"sourceHtmlUrl":97},"reference\u002Fcpp.md",7667,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fcpp.md",{"path":99,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":100,"sourceHtmlUrl":101},"reference\u002Fcss-less-sass.md",13113,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fcss-less-sass.md",{"path":103,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":104,"sourceHtmlUrl":105},"reference\u002Fgo.md",20279,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fgo.md",{"path":107,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":108,"sourceHtmlUrl":109},"reference\u002Fjava.md",10201,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fjava.md",{"path":111,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":112,"sourceHtmlUrl":113},"reference\u002Fperformance-review-guide.md",17573,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fperformance-review-guide.md",{"path":115,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":116,"sourceHtmlUrl":117},"reference\u002Fpython.md",24347,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fpython.md",{"path":119,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":120,"sourceHtmlUrl":121},"reference\u002Fqt.md",6153,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fqt.md",{"path":123,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":124,"sourceHtmlUrl":125},"reference\u002Freact.md",21979,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Freact.md",{"path":127,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":128,"sourceHtmlUrl":129},"reference\u002Frust.md",21030,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Frust.md",{"path":131,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":132,"sourceHtmlUrl":133},"reference\u002Fsecurity-review-guide.md",6836,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fsecurity-review-guide.md",{"path":135,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":136,"sourceHtmlUrl":137},"reference\u002Ftypescript.md",12883,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Ftypescript.md",{"path":139,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":140,"sourceHtmlUrl":141},"reference\u002Fvue.md",20499,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Freference\u002Fvue.md",{"path":143,"resourceType":144,"resourceTypeDesc":145,"sizeBytes":146,"sourceHtmlUrl":147},"scripts\u002Fpr-analyzer.py","SCRIPT","脚本",11213,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fcode-review-skill\u002Fscripts\u002Fpr-analyzer.py",[149,156,162,168,175,184],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"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":157,"name":151,"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":161,"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":163,"name":151,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"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":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"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":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":179,"licenseFileUrl":180,"sourceHtmlUrl":181,"categories":182,"keywords":183,"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":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"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",[],[]]