[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFWXREV3DS8TMWX6XGPS0M":3,"skill-same:01M6AFWXREV3DS8TMWX6XGPS0M":92},{"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":34,"publishedAt":57,"linkOnly":58,"markdownContent":59,"markdownBody":60,"frontMatter":61,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6AFWXREV3DS8TMWX6XGPS0M","code-review",null,"Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsentry\u002Fcode-review\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56],"review","code","code review","pull","when","changes","requests","reviews","reviewing pull requests","use","quality","feedback","engineering","sentry","engineering practices","code quality","pull requests","performance","security","design review","design","testing","2026-11-10 10:12:30",false,"---\nname: code-review\ndescription: Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.\n---\n\n# Sentry Code Review\n\nFollow these guidelines when reviewing code for Sentry projects.\n\n## Review Checklist\n\n### Identifying Problems\n\nLook for these issues in code changes:\n\n- **Runtime errors**: Potential exceptions, null pointer issues, out-of-bounds access\n- **Performance**: Unbounded O(n²) operations, N+1 queries, unnecessary allocations\n- **Side effects**: Unintended behavioral changes affecting other components\n- **Backwards compatibility**: Breaking API changes without migration path\n- **ORM queries**: Complex Django ORM with unexpected query performance\n- **Security vulnerabilities**: Injection, XSS, access control gaps, secrets exposure\n\n### Design Assessment\n\n- Do component interactions make logical sense?\n- Does the change align with existing project architecture?\n- Are there conflicts with current requirements or goals?\n\n### Test Coverage\n\nEvery PR should have appropriate test coverage:\n\n- Functional tests for business logic\n- Integration tests for component interactions\n- End-to-end tests for critical user paths\n\nVerify tests cover actual requirements and edge cases. Avoid excessive branching or looping in test code.\n\n### Long-Term Impact\n\nFlag for senior engineer review when changes involve:\n\n- Database schema modifications\n- API contract changes\n- New framework or library adoption\n- Performance-critical code paths\n- Security-sensitive functionality\n\n## Feedback Guidelines\n\n### Tone\n\n- Be polite and empathetic\n- Provide actionable suggestions, not vague criticism\n- Phrase as questions when uncertain: \"Have you considered...?\"\n\n### Approval\n\n- Approve when only minor issues remain\n- Don't block PRs for stylistic preferences\n- Remember: the goal is risk reduction, not perfect code\n\n## Common Patterns to Flag\n\n### Python\u002FDjango\n\n```python\n# Bad: N+1 query\nfor user in users:\n    print(user.profile.name)  # Separate query per user\n\n# Good: Prefetch related\nusers = User.objects.prefetch_related('profile')\n```\n\n### TypeScript\u002FReact\n\n```typescript\n\u002F\u002F Bad: Missing dependency in useEffect\nuseEffect(() => {\n  fetchData(userId);\n}, []);  \u002F\u002F userId not in deps\n\n\u002F\u002F Good: Include all dependencies\nuseEffect(() => {\n  fetchData(userId);\n}, [userId]);\n```\n\n### Security\n\n```python\n# Bad: SQL injection risk\ncursor.execute(f\"SELECT * FROM users WHERE id = {user_id}\")\n\n# Good: Parameterized query\ncursor.execute(\"SELECT * FROM users WHERE id = %s\", [user_id])\n```\n\n## References\n\n- [Sentry Code Review Guidelines](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcode-review\u002F)\n","# Sentry Code Review\n\nFollow these guidelines when reviewing code for Sentry projects.\n\n## Review Checklist\n\n### Identifying Problems\n\nLook for these issues in code changes:\n\n- **Runtime errors**: Potential exceptions, null pointer issues, out-of-bounds access\n- **Performance**: Unbounded O(n²) operations, N+1 queries, unnecessary allocations\n- **Side effects**: Unintended behavioral changes affecting other components\n- **Backwards compatibility**: Breaking API changes without migration path\n- **ORM queries**: Complex Django ORM with unexpected query performance\n- **Security vulnerabilities**: Injection, XSS, access control gaps, secrets exposure\n\n### Design Assessment\n\n- Do component interactions make logical sense?\n- Does the change align with existing project architecture?\n- Are there conflicts with current requirements or goals?\n\n### Test Coverage\n\nEvery PR should have appropriate test coverage:\n\n- Functional tests for business logic\n- Integration tests for component interactions\n- End-to-end tests for critical user paths\n\nVerify tests cover actual requirements and edge cases. Avoid excessive branching or looping in test code.\n\n### Long-Term Impact\n\nFlag for senior engineer review when changes involve:\n\n- Database schema modifications\n- API contract changes\n- New framework or library adoption\n- Performance-critical code paths\n- Security-sensitive functionality\n\n## Feedback Guidelines\n\n### Tone\n\n- Be polite and empathetic\n- Provide actionable suggestions, not vague criticism\n- Phrase as questions when uncertain: \"Have you considered...?\"\n\n### Approval\n\n- Approve when only minor issues remain\n- Don't block PRs for stylistic preferences\n- Remember: the goal is risk reduction, not perfect code\n\n## Common Patterns to Flag\n\n### Python\u002FDjango\n\n```python\n# Bad: N+1 query\nfor user in users:\n    print(user.profile.name)  # Separate query per user\n\n# Good: Prefetch related\nusers = User.objects.prefetch_related('profile')\n```\n\n### TypeScript\u002FReact\n\n```typescript\n\u002F\u002F Bad: Missing dependency in useEffect\nuseEffect(() => {\n  fetchData(userId);\n}, []);  \u002F\u002F userId not in deps\n\n\u002F\u002F Good: Include all dependencies\nuseEffect(() => {\n  fetchData(userId);\n}, [userId]);\n```\n\n### Security\n\n```python\n# Bad: SQL injection risk\ncursor.execute(f\"SELECT * FROM users WHERE id = {user_id}\")\n\n# Good: Parameterized query\ncursor.execute(\"SELECT * FROM users WHERE id = %s\", [user_id])\n```\n\n## References\n\n- [Sentry Code Review Guidelines](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcode-review\u002F)\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fsentry\u002Fcode-review",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add davila7\u002Fclaude-code-templates --skill code-review",{"tool":78,"command":79},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill code-review",{"tool":81,"command":82},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsentry\u002Fcode-review\u002FSKILL.md",true,[86],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"code-reviewer.md","REFERENCE","参考文档",3385,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers\u002Fskills\u002Frequesting-code-review\u002Fcode-reviewer.md",[93,121,147,178,213,234],{"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":102,"publishedAt":57},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[99],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[103,104,105,106,107,108,109,110,44,39,111,112,113,114,115,116,117,118,119,120],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":57},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[127],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},[129,130,131,132,133,134,135,136,137,138,139,39,36,140,141,142,143,144,145,146],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"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":160,"publishedAt":57},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[153,156,157],{"categoryNo":154,"categoryName":155,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":158,"categoryName":159,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师",[161,162,163,164,165,166,167,108,168,169,170,171,172,173,174,44,175,176,39,177],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":182,"licenseFileUrl":183,"sourceHtmlUrl":184,"categories":185,"keywords":189,"publishedAt":57},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[186],{"categoryNo":187,"categoryName":188,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,108,212],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":182,"licenseFileUrl":217,"sourceHtmlUrl":218,"categories":219,"keywords":222,"publishedAt":57},"01M6AFWF33SFV9Z3SF4PEEE4BF","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.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[220,221],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":187,"categoryName":188,"taxonomyType":21,"taxonomyTypeDesc":22},[223,56,224,225,226,191,227,200,201,228,229,230,231,108,232,112,233],"webapp testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":182,"licenseFileUrl":238,"sourceHtmlUrl":239,"categories":240,"keywords":248,"publishedAt":57},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[241,244,245],{"categoryNo":242,"categoryName":243,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":246,"categoryName":247,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[249,250,251,252,253,254,255,256,193,257,203,36,258,35,259,260,261,173,262,39,263,264,265,266,267,118,268],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]