[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZDXF3C5FE4GBX8V8GCV43":3,"skill-same:01M72ZDXF3C5FE4GBX8V8GCV43":79},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":13,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M72ZDXF3C5FE4GBX8V8GCV43","code-reviewer",null,"Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.","andrewthomastaylor\u002FSkills","andrewthomastaylor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249856925?v=4","01M72Z00NZWQPWA1TVXZPKXXWJ","01M72Z00PJ210Z6DAD1N93P2HG",0,"MIT","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fcode-reviewer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: code-reviewer\ndescription: Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.\nlicense: MIT\nallowed-tools: Read, Grep, Glob\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: quality\n  triggers: code review, PR review, pull request, review code, code quality\n  role: specialist\n  scope: review\n  output-format: report\n  related-skills: security-reviewer, test-master, architecture-designer\n---\n\n# Code Reviewer\n\nSenior engineer conducting thorough, constructive code reviews that improve quality and share knowledge.\n\n## When to Use This Skill\n\n- Reviewing pull requests\n- Conducting code quality audits\n- Identifying refactoring opportunities\n- Checking for security vulnerabilities\n- Validating architectural decisions\n\n## Core Workflow\n\n1. **Context** — Read PR description, understand the problem being solved. **Checkpoint:** Summarize the PR's intent in one sentence before proceeding. If you cannot, ask the author to clarify.\n2. **Structure** — Review architecture and design decisions. Ask: Does this follow existing patterns in the codebase? Are new abstractions justified?\n3. **Details** — Check code quality, security, and performance. Apply the checks in the Reference Guide below. Ask: Are there N+1 queries, hardcoded secrets, or injection risks?\n4. **Tests** — Validate test coverage and quality. Ask: Are edge cases covered? Do tests assert behavior, not implementation?\n5. **Feedback** — Produce a categorized report using the Output Template. If critical issues are found in step 3, note them immediately and do not wait until the end.\n\n> **Disagreement handling:** If the author has left comments explaining a non-obvious choice, acknowledge their reasoning before suggesting an alternative. Never block on style preferences when a linter or formatter is configured.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n\u003C!-- Spec Compliance and Receiving Feedback rows adapted from obra\u002Fsuperpowers by Jesse Vincent (@obra), MIT License -->\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Review Checklist | `references\u002Freview-checklist.md` | Starting a review, categories |\n| Common Issues | `references\u002Fcommon-issues.md` | N+1 queries, magic numbers, patterns |\n| Feedback Examples | `references\u002Ffeedback-examples.md` | Writing good feedback |\n| Report Template | `references\u002Freport-template.md` | Writing final review report |\n| Spec Compliance | `references\u002Fspec-compliance-review.md` | Reviewing implementations, PR review, spec verification |\n| Receiving Feedback | `references\u002Freceiving-feedback.md` | Responding to review comments, handling feedback |\n\n## Review Patterns (Quick Reference)\n\n### N+1 Query — Bad vs Good\n```python\n# BAD: query inside loop\nfor user in users:\n    orders = Order.objects.filter(user=user)  # N+1\n\n# GOOD: prefetch in bulk\nusers = User.objects.prefetch_related('orders').all()\n```\n\n### Magic Number — Bad vs Good\n```python\n# BAD\nif status == 3:\n    ...\n\n# GOOD\nORDER_STATUS_SHIPPED = 3\nif status == ORDER_STATUS_SHIPPED:\n    ...\n```\n\n### Security: SQL Injection — Bad vs Good\n```python\n# BAD: string interpolation in query\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## Constraints\n\n### MUST DO\n- Summarize PR intent before reviewing (see Workflow step 1)\n- Provide specific, actionable feedback\n- Include code examples in suggestions\n- Praise good patterns\n- Prioritize feedback (critical → minor)\n- Review tests as thoroughly as code\n- Check for security issues (OWASP Top 10 as baseline)\n\n### MUST NOT DO\n- Be condescending or rude\n- Nitpick style when linters exist\n- Block on personal preferences\n- Demand perfection\n- Review without understanding the why\n- Skip praising good work\n\n## Output Template\n\nCode review report must include:\n1. **Summary** — One-sentence intent recap + overall assessment\n2. **Critical issues** — Must fix before merge (bugs, security, data loss)\n3. **Major issues** — Should fix (performance, design, maintainability)\n4. **Minor issues** — Nice to have (naming, readability)\n5. **Positive feedback** — Specific patterns done well\n6. **Questions for author** — Clarifications needed\n7. **Verdict** — Approve \u002F Request Changes \u002F Comment\n\n## Knowledge Reference\n\nSOLID, DRY, KISS, YAGNI, design patterns, OWASP Top 10, language idioms, testing patterns\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fquality\u002Fcode-reviewer\u002F)\n","# Code Reviewer\n\nSenior engineer conducting thorough, constructive code reviews that improve quality and share knowledge.\n\n## When to Use This Skill\n\n- Reviewing pull requests\n- Conducting code quality audits\n- Identifying refactoring opportunities\n- Checking for security vulnerabilities\n- Validating architectural decisions\n\n## Core Workflow\n\n1. **Context** — Read PR description, understand the problem being solved. **Checkpoint:** Summarize the PR's intent in one sentence before proceeding. If you cannot, ask the author to clarify.\n2. **Structure** — Review architecture and design decisions. Ask: Does this follow existing patterns in the codebase? Are new abstractions justified?\n3. **Details** — Check code quality, security, and performance. Apply the checks in the Reference Guide below. Ask: Are there N+1 queries, hardcoded secrets, or injection risks?\n4. **Tests** — Validate test coverage and quality. Ask: Are edge cases covered? Do tests assert behavior, not implementation?\n5. **Feedback** — Produce a categorized report using the Output Template. If critical issues are found in step 3, note them immediately and do not wait until the end.\n\n> **Disagreement handling:** If the author has left comments explaining a non-obvious choice, acknowledge their reasoning before suggesting an alternative. Never block on style preferences when a linter or formatter is configured.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n\u003C!-- Spec Compliance and Receiving Feedback rows adapted from obra\u002Fsuperpowers by Jesse Vincent (@obra), MIT License -->\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Review Checklist | `references\u002Freview-checklist.md` | Starting a review, categories |\n| Common Issues | `references\u002Fcommon-issues.md` | N+1 queries, magic numbers, patterns |\n| Feedback Examples | `references\u002Ffeedback-examples.md` | Writing good feedback |\n| Report Template | `references\u002Freport-template.md` | Writing final review report |\n| Spec Compliance | `references\u002Fspec-compliance-review.md` | Reviewing implementations, PR review, spec verification |\n| Receiving Feedback | `references\u002Freceiving-feedback.md` | Responding to review comments, handling feedback |\n\n## Review Patterns (Quick Reference)\n\n### N+1 Query — Bad vs Good\n```python\n# BAD: query inside loop\nfor user in users:\n    orders = Order.objects.filter(user=user)  # N+1\n\n# GOOD: prefetch in bulk\nusers = User.objects.prefetch_related('orders').all()\n```\n\n### Magic Number — Bad vs Good\n```python\n# BAD\nif status == 3:\n    ...\n\n# GOOD\nORDER_STATUS_SHIPPED = 3\nif status == ORDER_STATUS_SHIPPED:\n    ...\n```\n\n### Security: SQL Injection — Bad vs Good\n```python\n# BAD: string interpolation in query\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## Constraints\n\n### MUST DO\n- Summarize PR intent before reviewing (see Workflow step 1)\n- Provide specific, actionable feedback\n- Include code examples in suggestions\n- Praise good patterns\n- Prioritize feedback (critical → minor)\n- Review tests as thoroughly as code\n- Check for security issues (OWASP Top 10 as baseline)\n\n### MUST NOT DO\n- Be condescending or rude\n- Nitpick style when linters exist\n- Block on personal preferences\n- Demand perfection\n- Review without understanding the why\n- Skip praising good work\n\n## Output Template\n\nCode review report must include:\n1. **Summary** — One-sentence intent recap + overall assessment\n2. **Critical issues** — Must fix before merge (bugs, security, data loss)\n3. **Major issues** — Should fix (performance, design, maintainability)\n4. **Minor issues** — Nice to have (naming, readability)\n5. **Positive feedback** — Specific patterns done well\n6. **Questions for author** — Clarifications needed\n7. **Verdict** — Approve \u002F Request Changes \u002F Comment\n\n## Knowledge Reference\n\nSOLID, DRY, KISS, YAGNI, design patterns, OWASP Top 10, language idioms, testing patterns\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fquality\u002Fcode-reviewer\u002F)\n",{"name":5,"license":14,"metadata":23,"description":7,"allowed-tools":32},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"specialist","review","https:\u002F\u002Fgithub.com\u002FJeffallan","quality","1.1.0","code review, PR review, pull request, review code, code quality","report","security-reviewer, test-master, architecture-designer","Read, Grep, Glob","main","cb7b4065bacb4b06224de86d509ccef568f68b79","claude-skills\u002Fskills\u002Fcode-reviewer","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor","2026-05-29 06:53:07",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add andrewthomastaylor\u002FSkills --skill code-reviewer",{"tool":45,"command":46},"bunx","bunx skills add andrewthomastaylor\u002FSkills --skill code-reviewer",{"tool":48,"command":49},"pnpm","pnpm dlx skills add andrewthomastaylor\u002FSkills --skill code-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fcode-reviewer\u002FSKILL.md",true,[53,59,63,67,71,75],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fcommon-issues.md","REFERENCE","参考文档",2999,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fcode-reviewer\u002Freferences\u002Fcommon-issues.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Ffeedback-examples.md",3458,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fcode-reviewer\u002Freferences\u002Ffeedback-examples.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Freceiving-feedback.md",6680,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fcode-reviewer\u002Freferences\u002Freceiving-feedback.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Freport-template.md",3075,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fcode-reviewer\u002Freferences\u002Freport-template.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Freview-checklist.md",2485,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fcode-reviewer\u002Freferences\u002Freview-checklist.md",{"path":76,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fspec-compliance-review.md",9009,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fcode-reviewer\u002Freferences\u002Fspec-compliance-review.md",[80,89,97,104,111,118],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M732GDQJ0CWHBAW4D7ENMA3N","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M731QVEE2QCT389Z3X1JWFVQ","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M731AMWEC72GFFNFS55F0TTC","returns-reverse-logistics","Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":18},"01M7319BJFM3CBX39C85QWSMD1","quality-nonconformance","Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":18},"01M7318DPHWK6CEVCVT7PHNKDZ","production-scheduling","Codified expertise for production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC\u002Fdrum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP\u002FMES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fproduction-scheduling\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":18},"01M7315ZE0J0AB6KTQAFGCYF5V","logistics-exception-management","Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Flogistics-exception-management\u002FSKILL.md",[],[]]